From: Jakub Sitnicki <jakub@cloudflare.com>
To: Hsin-Wei Hung <hsinweih@uci.edu>
Cc: John Fastabend <john.fastabend@gmail.com>,
"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: Thu, 23 Feb 2023 14:17:54 +0100 [thread overview]
Message-ID: <87a614h62a.fsf@cloudflare.com> (raw)
In-Reply-To: <CABcoxUayum5oOqFMMqAeWuS8+EzojquSOSyDA3J_2omY=2EeAg@mail.gmail.com>
Hi,
On Mon, Feb 20, 2023 at 07:39 AM -06, Hsin-Wei Hung wrote:
> I think my previous report got blocked since it contained HTML
> subparts so I am sending it again. 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.
Not sure if you've seen John's reply to the previous report:
https://lore.kernel.org/all/63dddcc92fc31_6bb15208e9@john.notmuch/
Are you also fuzzing any newer kernel versions? Or was v5.19 the latest?
Did syzkaller find a reproducer?
Thanks,
Jakub
next prev parent reply other threads:[~2023-02-23 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 13:39 A potential deadlock in sockhash map Hsin-Wei Hung
2023-02-23 13:17 ` Jakub Sitnicki [this message]
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
[not found] <CABcoxUbyxuEaciKLpSeGN-0xnf8H1w1CV9BDZi8++cWhKtQQXw@mail.gmail.com>
2023-02-04 4:19 ` John Fastabend
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=87a614h62a.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hsinweih@uci.edu \
--cc=john.fastabend@gmail.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.