netdev - Re: [PATCH bpf] xsk: Initialise xskb free_list

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20211229100326.4f398952@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date:   Wed, 29 Dec 2021 10:03:26 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc:     Magnus Karlsson <magnus.karlsson@...il.com>,
        "Loftus, Ciara" <ciara.loftus@...el.com>,
        "Karlsson, Magnus" <magnus.karlsson@...el.com>,
        Björn Töpel <bjorn@...nel.org>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Network Development <netdev@...r.kernel.org>,
        "Fijalkowski, Maciej" <maciej.fijalkowski@...el.com>,
        bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH bpf] xsk: Initialise xskb free_list_node

On Tue, 28 Dec 2021 19:04:10 -0800 Alexei Starovoitov wrote:
> > My $0.02 would be that if all relevant commits form a chain of fixes
> > it doesn't matter much which one you put in the tag. To me your
> > suggestion of going with 199d983bc015 makes most sense since from a
> > cursory look the direct issue doesn't really exist without that commit.
> >
> > Plus we probably don't want 199d983bc015 to be backported until we
> > apply this fix, so it'd be good if "Fixes: 199d983bc015" appeared in
> > linux-next.
> >
> > You can always put multiple Fixes tags on the commit, if you're unsure.  
> 
> It sounds that the fix should get into net and linus tree asap?
> In such a case mabe take it into net directly?

Ack