From: patchwork-bot+netdevbpf@kernel.org
To: Avinash Duduskar <avinash.duduskar@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
memxor@gmail.com, shuah@kernel.org, eddyz87@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, toke@redhat.com,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix fib_lookup VLAN tests on hosts with forwarding on
Date: Wed, 15 Jul 2026 11:20:05 +0000 [thread overview]
Message-ID: <178411440591.4020782.15937168768043001912.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260715100349.2684391-1-avinash.duduskar@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 15 Jul 2026 15:33:49 +0530 you wrote:
> The VLAN tests assume the test namespace starts with IPv4 forwarding off,
> but a new netns copies conf/all and conf/default from init_net
> (devinet_init_net(), with net.core.devconf_inherit_init_net at its
> default), so on a host with net.ipv4.conf.all.forwarding=1 the devices in
> the netns come up with forwarding already enabled. IPv6 uses compiled
> defaults at the same sysctl value, so only the IPv4 arms are affected.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Fix fib_lookup VLAN tests on hosts with forwarding on
https://git.kernel.org/bpf/bpf-next/c/d1f4b56417a3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-15 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 10:03 Avinash Duduskar
2026-07-15 11:20 ` 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=178411440591.4020782.15937168768043001912.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=avinash.duduskar@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=toke@redhat.com \
--cc=yonghong.song@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox