linux-kernel - Re: [PULL] Networking for v6.1 final / v6.1-rc9 (with the diff stat :S)

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:   Fri, 9 Dec 2022 17:27:59 -0800
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        "David S. Miller" <davem@...emloft.net>,
        Network Development <netdev@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Jiri Olsa <olsajiri@...il.com>, Yonghong Song <yhs@...a.com>
Subject: Re: [PULL] Networking for v6.1 final / v6.1-rc9 (with the diff stat :S)

On Fri, Dec 9, 2022 at 2:05 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Fri, 9 Dec 2022 13:00:01 -0800 Jakub Kicinski wrote:
> > On Fri, 9 Dec 2022 10:25:09 -0800 Linus Torvalds wrote:
> > > > There is an outstanding regression in BPF / Peter's static calls stuff,
> > >
> > > Looks like it's not related to the static calls. Jiri says that
> > > reverting that static call change makes no difference, and currently
> > > suspects a RCU race instead:
> > >
> > >   https://lore.kernel.org/bpf/Y5M9P95l85oMHki9@krava/T/#t
> > >
> > > Hmm?
> >
> > Yes. I can't quickly grok how the static call changes impacted
> > the locking. I'll poke the BPF people to give us a sense of urgency.
> > IDK how likely it is to get hold of Peter Z..
>
> Adding Alexei et al. to the CC.
> What I understood from off-list comments is the issue is not
> a showstopper and synchronize_rcu_tasks() seems like a good fix.

Confirming. The bug is not a show stopper.
The nature of the bug still needs to be understood though.