From: syzbot <syzbot+bacb240dbeebb88518ae@syzkaller.appspotmail.com>
To: boqun.feng@gmail.com, daniel@iogearbox.net, hdanton@sina.com,
jakub@cloudflare.com, john.fastabend@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
torvalds@linux-foundation.org
Subject: Re: [syzbot] [kernel?] possible deadlock in __hrtimer_run_queues (2)
Date: Thu, 06 Jun 2024 19:51:02 -0700 [thread overview]
Message-ID: <000000000000c31e9f061a43de90@google.com> (raw)
In-Reply-To: <00000000000002a89b06146e6ecb@google.com>
syzbot suspects this issue was fixed by commit:
commit ff91059932401894e6c86341915615c5eb0eca48
Author: Jakub Sitnicki <jakub@cloudflare.com>
Date: Tue Apr 2 10:46:21 2024 +0000
bpf, sockmap: Prevent lock inversion deadlock in map delete elem
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1169a80a980000
start commit: 61df575632d6 libbpf: Add new sec_def "sk_skb/verdict"
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
dashboard link: https://syzkaller.appspot.com/bug?extid=bacb240dbeebb88518ae
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1793a2e6180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c8dac9180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bpf, sockmap: Prevent lock inversion deadlock in map delete elem
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-06-07 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000002a89b06146e6ecb@google.com>
2024-03-25 0:54 ` [syzbot] [kernel?] possible deadlock in __hrtimer_run_queues (2) syzbot
2024-06-07 2:51 ` syzbot [this message]
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=000000000000c31e9f061a43de90@google.com \
--to=syzbot+bacb240dbeebb88518ae@syzkaller.appspotmail.com \
--cc=boqun.feng@gmail.com \
--cc=daniel@iogearbox.net \
--cc=hdanton@sina.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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).