linux-kernel - Re: [PATCH v2] tracing/ipv4/ipv6: Use static array for name field in fib*_lookup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 5 Jul 2022 12:18:43 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     David Ahern <dsahern@...il.com>,
        LKML <linux-kernel@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>,
        netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v2] tracing/ipv4/ipv6: Use static array for name field
 in fib*_lookup_table event

On Tue, 5 Jul 2022 10:00:41 -0400 Steven Rostedt wrote:
> On Mon, 4 Jul 2022 13:09:01 -0600
> David Ahern <dsahern@...il.com> wrote:
> 
> > >  include/trace/events/fib.h  | 6 +++---
> > >  include/trace/events/fib6.h | 8 ++++----
> > >  2 files changed, 7 insertions(+), 7 deletions(-)
> > >     
> > 
> > Reviewed-by: David Ahern <dsahern@...nel.org>
> >   
> 
> Is everyone OK if I take this through my tree then?
> 
> I'm fine if it goes through net-next too.

Slight risk of conflicts there if someone decides to add another FIB
trace point, but seems unlikely so feel free to take it:

Acked-by: Jakub Kicinski <kuba@...nel.org>