All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Hsin-Wei Hung <hsinweih@uci.edu>,
	John Fastabend <john.fastabend@gmail.com>,
	Jakub Sitnicki <jakub@cloudflare.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: RE: A potential deadlock in sockhash map
Date: Fri, 03 Feb 2023 20:19:21 -0800	[thread overview]
Message-ID: <63dddcc92fc31_6bb15208e9@john.notmuch> (raw)
In-Reply-To: <CABcoxUbyxuEaciKLpSeGN-0xnf8H1w1CV9BDZi8++cWhKtQQXw@mail.gmail.com>

Hsin-Wei Hung wrote:
> Hi,
> 
> Our bpf runtime fuzzer (a customized syzkaller) triggered a lockdep warning
> in the bpf subsystem indicating a potential deadlock. We are able to
> trigger this bug on v5.15.25 and v5.19. The following code is a BPF PoC,
> and the lockdep warning is attached at the end.

Thanks, but can you test the latest kernel?

Or at least latest 5.15 stable, 5.15.25 is a bit old and is missing lots of
fixes. And 5.19 is not even a LTS so wouldn't have many fixes.

Ideally if possible testing bpf tree would be the most helpful.

 https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/

I believe we fixed a similar bug already so hoping this is just hitting an
already fixed bug. But, would be best to confirm thanks.

Thanks,
John

       reply	other threads:[~2023-02-04  4:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABcoxUbyxuEaciKLpSeGN-0xnf8H1w1CV9BDZi8++cWhKtQQXw@mail.gmail.com>
2023-02-04  4:19 ` John Fastabend [this message]
2023-02-20 13:39 A potential deadlock in sockhash map Hsin-Wei Hung
2023-02-23 13:17 ` Jakub Sitnicki
2023-02-24 15:58   ` Hsin-Wei Hung
2023-02-24 19:18     ` Hsin-Wei Hung
2023-02-24 20:26       ` John Fastabend
2023-03-12 19:32 ` Cong Wang

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=63dddcc92fc31_6bb15208e9@john.notmuch \
    --to=john.fastabend@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hsinweih@uci.edu \
    --cc=jakub@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.