Skip to content

v1.19 Backports 2026-01-22#43922

Merged
giorio94 merged 7 commits intov1.19from
pr/v1.19-backport-2026-01-22-12-24
Jan 22, 2026
Merged

v1.19 Backports 2026-01-22#43922
giorio94 merged 7 commits intov1.19from
pr/v1.19-backport-2026-01-22-12-24

Conversation

@giorio94
Copy link
Copy Markdown
Member

@giorio94 giorio94 commented Jan 22, 2026

borkmann and others added 7 commits January 22, 2026 12:24
[ upstream commit f87ff38 ]

In IPv4 code, we pull the ARP header into the linear section of the skb:

  [...]
  case bpf_htons(ETH_P_ARP):
    if (is_defined(ENABLE_ARP_PASSTHROUGH) ||
        is_defined(ENABLE_ARP_RESPONDER) ||
        CONFIG(enable_l2_announcements)) {
        if (!revalidate_data_arp_pull(ctx, &data, &data_end, &arp)) {
	  ret = DROP_INVALID;
	  goto drop_err_ingress;
        }

        [...]

        if (CONFIG(enable_l2_announcements)) {
          ret = handle_l2_announcement(ctx, NULL);
       [...]

This is however not the case in IPv6, and so a NIC driver which does not
pull in anything the handle_l2_announcement() could fail given only the
Ethernet + IPv6 header is in the linear section. Then we return with
CTX_ACT_OK and the packet goes up the stack. Given this is slow-path, pull
in skb->len. For XDP its a no-op.

Related: #43774
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Co-developed-by: Marc Suñé <marc.sune@isovalent.com>
Signed-off-by: Marc Suñé <marc.sune@isovalent.com>
Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
…f ipsec

[ upstream commit 4f5a008 ]

Currently, we regenerate the host endpoint before all other restored endpoints
if IPSec is enabled.

This might be problematic as it increases the overall time for the endpoint
restoration - and might lead to issues if Envoy prematurely configures
Envoy before all Endpoints are restored (default after 3 min).

It looks like this code / special handling is no longer needed with v1.19.
Let's remove it.

Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
[ upstream commit b7c4147 ]

The previous commit updating short ICMP error packet NAT
handling improperly computed the length of a short packet
by neglecting to account for the ihl field of the IP header
representing 32 bit words rather than bytes.  This caused
a reversion of #33844.

Furthermore, the change in short packet detection depends on
the incoming bpf_context structure having the "len" field set
correctly, which the BPF tests for that condition did not set.

This corrects the comparison for the inner L4 packet length
and updates the short ICMP error packet BPF tests to ensure
the ctx->len field is set like the kernel does.

Fixes: 1a018d56d623 ("bpf: Refine inner packet L4 checksum detection")

Signed-off-by: Bill Reese <ReeseW@computer.org>
Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
[ upstream commit aecd248 ]

This time should have a shorter timeout so it doesn't take 1h30m of CI
in case the step fails as seen in [1]. Since this step takes around 4
minutes on a successful run [2], 10 minutes of timeout seems to be a
good limit.

[1] https://github.com/cilium/cilium/actions/runs/21205723313/job/61001679788
[2] https://github.com/cilium/cilium/actions/runs/21216876084/job/61040455144

Signed-off-by: André Martins <andre@cilium.io>
Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
[ upstream commit 517f163 ]

Signed-off-by: xtine <xtineskim@gmail.com>
Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
[ upstream commit b197d98 ]

Signed-off-by: xtine <xtineskim@gmail.com>
Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
[ upstream commit 700b07e ]

Re-add workflow_dispatch so that ariane can trigger this workflow on a
scheduled basis since non-default branches don't support schedule event
triggers made by GitHub.

Signed-off-by: André Martins <andre@cilium.io>
Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
@giorio94 giorio94 added kind/backports This PR provides functionality previously merged into master. backport/1.19 This PR represents a backport for Cilium 1.19.x of a PR that was merged to main. labels Jan 22, 2026
@giorio94
Copy link
Copy Markdown
Member Author

/test

@giorio94 giorio94 marked this pull request as ready for review January 22, 2026 13:14
@giorio94 giorio94 requested review from a team as code owners January 22, 2026 13:14
@giorio94 giorio94 requested a review from brlbil January 22, 2026 13:14
@giorio94 giorio94 added this pull request to the merge queue Jan 22, 2026
Merged via the queue into v1.19 with commit d461be6 Jan 22, 2026
538 of 545 checks passed
@giorio94 giorio94 deleted the pr/v1.19-backport-2026-01-22-12-24 branch January 22, 2026 16:45
@cilium-release-bot cilium-release-bot bot moved this to Released in cilium v1.19.0 Feb 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/1.19 This PR represents a backport for Cilium 1.19.x of a PR that was merged to main. kind/backports This PR provides functionality previously merged into master.

Projects

No open projects
Status: Released

Development

Successfully merging this pull request may close these issues.

9 participants