From: syzbot <syzbot+9d95beb2a3c260622518@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, elic@nvidia.com,
haoluo@google.com, hdanton@sina.com, jasowang@redhat.com,
john.fastabend@gmail.com, jolsa@kernel.org, kafai@fb.com,
kpsingh@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, lkp@intel.com,
llvm@lists.linux.dev, martin.lau@linux.dev,
mathieu.desnoyers@efficios.com, memxor@gmail.com,
mhiramat@kernel.org, michal.kukowski@infogain.com,
michal.switala@infogain.com, mst@redhat.com,
netdev@vger.kernel.org, norbert.kaminski@igglobal.com,
norbert.kaminski@infogain.com, norkam41@gmail.com,
oe-kbuild-all@lists.linux.dev, parav@nvidia.com,
rostedt@goodmis.org, sdf@fomichev.me, sdf@google.com,
song@kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, wojciech.gladysz@infogain.com,
yhs@fb.com, yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] possible deadlock in trie_delete_elem
Date: Thu, 08 May 2025 00:13:03 -0700 [thread overview]
Message-ID: <681c597f.050a0220.a19a9.00bd.GAE@google.com> (raw)
In-Reply-To: <000000000000adb08b061413919e@google.com>
syzbot suspects this issue was fixed by commit:
commit 47979314c0fe245ed54306e2f91b3f819c7c0f9f
Author: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Date: Sun Mar 16 04:05:37 2025 +0000
bpf: Convert lpm_trie.c to rqspinlock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=140598f4580000
start commit: c2933b2befe2 Merge tag 'net-6.14-rc1' of git://git.kernel...
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=d033b14aeef39158
dashboard link: https://syzkaller.appspot.com/bug?extid=9d95beb2a3c260622518
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108e1724580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=177035f8580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bpf: Convert lpm_trie.c to rqspinlock
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-05-08 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 8:42 [syzbot] [bpf?] possible deadlock in trie_delete_elem syzbot
2024-03-20 14:20 ` syzbot
2025-05-08 7:13 ` syzbot [this message]
2025-05-08 18:00 ` Alexei Starovoitov
2025-05-08 23:39 ` Kumar Kartikeya Dwivedi
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=681c597f.050a0220.a19a9.00bd.GAE@google.com \
--to=syzbot+9d95beb2a3c260622518@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=elic@nvidia.com \
--cc=haoluo@google.com \
--cc=hdanton@sina.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=memxor@gmail.com \
--cc=mhiramat@kernel.org \
--cc=michal.kukowski@infogain.com \
--cc=michal.switala@infogain.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=norbert.kaminski@igglobal.com \
--cc=norbert.kaminski@infogain.com \
--cc=norkam41@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=parav@nvidia.com \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wojciech.gladysz@infogain.com \
--cc=yhs@fb.com \
--cc=yonghong.song@linux.dev \
/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