All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Feng Yang <yangfeng59949@163.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, posk@google.com,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, bpf@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v10 bpf-next 0/2] Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap
Date: Thu, 05 Mar 2026 01:10:07 +0000	[thread overview]
Message-ID: <177267300705.2465987.7557394320965019773.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260304094429.168521-1-yangfeng59949@163.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Wed,  4 Mar 2026 17:44:27 +0800 you wrote:
> From: Feng Yang <yangfeng@kylinos.cn>
> 
> Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap
> 
> Changes in v10:
> - Optimization patch. Thanks, Martin KaFai Lau.
> - Link to v9: https://lore.kernel.org/all/20260303074423.172680-1-yangfeng59949@163.com/
> Changes in v9:
> - Use dst_hold() and skb_dst_set().
>   !skb_dst skip.
>   Move all changes into the IS_ENABLED(CONFIG_IPV6).
>   Use #if IS_ENABLED(CONFIG_IPV6); otherwise, a compilation error will occur when ipv6 is not enabled.
>   Thanks, Martin KaFai Lau.
> - Link to v8: https://lore.kernel.org/all/20260227082133.96951-1-yangfeng59949@163.com/
> Changes in v8:
> - set ret to an error code before goto out.
> - Link to v7: https://lore.kernel.org/all/20260226095156.117996-1-yangfeng59949@163.com/
> Changes in v7:
> - Use ip6_null_entry to avoid. Thanks, Martin KaFai Lau.
> Changes in v6:
> - Modify the bpf_lwt_xmit_push_encap function and add selftests for it.
>   Thanks, Martin KaFai Lau.
> - Link to v5: https://lore.kernel.org/all/20260210090657.86977-1-yangfeng59949@163.com/
> Changes in v5:
> - Refer to the bpf_lwt_xmit_reroute function to configure the dst parameter.
> - Link to v4: https://lore.kernel.org/all/20260209015111.28144-1-yangfeng59949@163.com/
> Changes in v4:
> - add rcu lock
> - Link to v3: https://lore.kernel.org/all/20260206055113.63476-1-yangfeng59949@163.com/
> Changes in v3:
> - use dst_init
> - Link to v2: https://lore.kernel.org/all/20260205092227.126665-1-yangfeng59949@163.com/
> Changes in v2:
> - Link to v1: https://lore.kernel.org/all/20260127084520.13890-1-luyun_611@163.com/
> 
> [...]

Here is the summary with links:
  - [v10,bpf-next,1/2] bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap
    https://git.kernel.org/bpf/bpf-next/c/972787479ee7
  - [v10,bpf-next,2/2] selftests/bpf: Add selftests for the invocation of bpf_lwt_xmit_push_encap
    https://git.kernel.org/bpf/bpf-next/c/e8ae16d65ac6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-03-05  1:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  9:44 [PATCH v10 bpf-next 0/2] Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap Feng Yang
2026-03-04  9:44 ` [PATCH v10 bpf-next 1/2] bpf: test_run: " Feng Yang
2026-03-04 10:30   ` bot+bpf-ci
2026-03-04 10:33   ` Leon Hwang
2026-03-05  1:12     ` Martin KaFai Lau
2026-03-04  9:44 ` [PATCH v10 bpf-next 2/2] selftests/bpf: Add selftests for the invocation of bpf_lwt_xmit_push_encap Feng Yang
2026-03-04 10:33   ` Leon Hwang
2026-03-05  1:11     ` Martin KaFai Lau
2026-03-05  1:34       ` Leon Hwang
2026-03-05  1:10 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177267300705.2465987.7557394320965019773.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=posk@google.com \
    --cc=yangfeng59949@163.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.