[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000c31e9f061a43de90@google.com>
Date: Thu, 06 Jun 2024 19:51:02 -0700
From: syzbot <syzbot+bacb240dbeebb88518ae@...kaller.appspotmail.com>
To: boqun.feng@...il.com, daniel@...earbox.net, hdanton@...a.com,
jakub@...udflare.com, john.fastabend@...il.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, penguin-kernel@...ove.sakura.ne.jp,
syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
torvalds@...ux-foundation.org
Subject: Re: [syzbot] [kernel?] possible deadlock in __hrtimer_run_queues (2)
syzbot suspects this issue was fixed by commit:
commit ff91059932401894e6c86341915615c5eb0eca48
Author: Jakub Sitnicki <jakub@...udflare.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
Powered by blists - more mailing lists