From: Ido Schimmel <idosch@nvidia.com>
To: Ferenc Fejes <ferenc@fejes.dev>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@kernel.org, dsahern@kernel.org,
horms@kernel.org, petrm@nvidia.com, rostedt@goodmis.org,
daniel@iogearbox.net
Subject: Re: [PATCH net-next 0/3] Report netns cookie in FIB lookup tracepoints
Date: Wed, 7 Oct 2026 15:50:35 +0300 [thread overview]
Message-ID: <20261007125035.GA1047569@shredder> (raw)
In-Reply-To: <364f670e60754319fab25302b2b49e3269ec49da.camel@fejes.dev>
On Wed, Oct 07, 2026 at 02:34:51PM +0200, Ferenc Fejes wrote:
> I wonder if the parameter passing itself, e.g. the line
> +int fib_table_lookup(struct net *net, struct fib_table *tb, ...
> can be a standalone change. It would introduce no functional or user-
> facing changes and could therefore target the "net" tree, with the
> potential to be backported. Pure kfunc/kprobe-based eBPF tracers could
> benefit from that, with the downside of introducing an unused variable.
> I assume this would be a hard sell, to say the least :-)
Linus is asking maintainers to limit the rc pull requests to regression
/ security fixes, so it's unlikely that such a change would be routed
via the "net" tree.
> For the whole set:
> Reviewed-by: Ferenc Fejes <ferenc@fejes.dev>
Thanks!
prev parent reply other threads:[~2026-10-07 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 15:54 [PATCH net-next 0/3] Report netns cookie in FIB lookup tracepoints Ido Schimmel
2026-10-06 15:54 ` [PATCH net-next 1/3] ipv6: Report netns cookie in fib6_table_lookup tracepoint Ido Schimmel
2026-10-06 15:54 ` [PATCH net-next 2/3] ipv4: Pass netns to fib_table_lookup() Ido Schimmel
2026-10-07 23:16 ` netdev-bot+sashiko
2026-10-08 10:30 ` Ido Schimmel
2026-10-06 15:54 ` [PATCH net-next 3/3] ipv4: Report netns cookie in fib_table_lookup tracepoint Ido Schimmel
2026-10-07 12:34 ` [PATCH net-next 0/3] Report netns cookie in FIB lookup tracepoints Ferenc Fejes
2026-10-07 12:50 ` Ido Schimmel [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=20261007125035.GA1047569@shredder \
--to=idosch@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=ferenc@fejes.dev \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=rostedt@goodmis.org \
/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