From: David Ahern <dsahern@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@kernel.org, horms@kernel.org, rostedt@goodmis.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
daniel@iogearbox.net, petrm@nvidia.com, ferenc@fejes.dev
Subject: Re: [PATCH net-next v2 3/3] ipv4: Report netns cookie in fib_table_lookup tracepoint
Date: Sat, 10 Oct 2026 07:34:23 -0600 [thread overview]
Message-ID: <9dc71ab5-9cab-4404-aacf-b05fa083e58c@kernel.org> (raw)
In-Reply-To: <20261008133158.1438907-4-idosch@nvidia.com>
On 10/8/26 7:31 AM, Ido Schimmel wrote:
> The fib_table_lookup tracepoint does not report the network namespace in
> which the lookup was performed, making it impossible to tell apart
> lookups performed in different namespaces.
>
> Report the network namespace cookie now that the namespace is passed to
> the tracepoint.
>
> Assisted-by: LLM
> Reviewed-by: Petr Machata <petrm@nvidia.com>
> Reviewed-by: Ferenc Fejes <ferenc@fejes.dev>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
>
> Notes:
> Sashiko: There is a pre-existing issue here regarding an uninitialized
> gateway address. I will take care of it separately.
>
> include/trace/events/fib.h | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
prev parent reply other threads:[~2026-10-10 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 13:31 [PATCH net-next v2 0/3] Report netns cookie in FIB lookup tracepoints Ido Schimmel
2026-10-08 13:31 ` [PATCH net-next v2 1/3] ipv6: Report netns cookie in fib6_table_lookup tracepoint Ido Schimmel
2026-10-10 13:33 ` David Ahern
2026-10-08 13:31 ` [PATCH net-next v2 2/3] ipv4: Pass netns to fib_table_lookup() Ido Schimmel
2026-10-10 13:34 ` David Ahern
2026-10-08 13:31 ` [PATCH net-next v2 3/3] ipv4: Report netns cookie in fib_table_lookup tracepoint Ido Schimmel
2026-10-10 13:34 ` David Ahern [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=9dc71ab5-9cab-4404-aacf-b05fa083e58c@kernel.org \
--to=dsahern@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=ferenc@fejes.dev \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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