From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jiri Olsa <olsajiri@gmail.com>, Yonghong Song <yhs@meta.com>
Subject: Re: [PULL] Networking for v6.1 final / v6.1-rc9 (with the diff stat :S)
Date: Fri, 9 Dec 2022 17:27:59 -0800 [thread overview]
Message-ID: <CAADnVQJmXAD3nC+TU7x2pL4tm07XupDDwf2thGcpfGSJ09u9+A@mail.gmail.com> (raw)
In-Reply-To: <20221209140550.571e6b65@kernel.org>
On Fri, Dec 9, 2022 at 2:05 PM Jakub Kicinski <kuba@kernel.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.
next prev parent reply other threads:[~2022-12-10 1:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 20:56 [PULL] Networking for v6.1 final / v6.1-rc9 Jakub Kicinski
2022-12-08 21:00 ` [PULL] Networking for v6.1 final / v6.1-rc9 (with the diff stat :S) Jakub Kicinski
2022-12-09 18:25 ` Linus Torvalds
2022-12-09 21:00 ` Jakub Kicinski
2022-12-09 22:05 ` Jakub Kicinski
2022-12-10 1:27 ` Alexei Starovoitov [this message]
2022-12-08 23:57 ` [PULL] Networking for v6.1 final / v6.1-rc9 pr-tracker-bot
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=CAADnVQJmXAD3nC+TU7x2pL4tm07XupDDwf2thGcpfGSJ09u9+A@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=pabeni@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=yhs@meta.com \
/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;
as well as URLs for NNTP newsgroup(s).