All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, 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 14:05:50 -0800	[thread overview]
Message-ID: <20221209140550.571e6b65@kernel.org> (raw)
In-Reply-To: <20221209130001.0f90f7f8@kernel.org>

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.

  reply	other threads:[~2022-12-09 22:06 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 [this message]
2022-12-10  1:27         ` Alexei Starovoitov
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=20221209140550.571e6b65@kernel.org \
    --to=kuba@kernel.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.