From: syzbot <syzbot+1a93ee5d329e97cfbaff@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
brauner@kernel.org, daniel@iogearbox.net, elic@nvidia.com,
haoluo@google.com, jakub@cloudflare.com, jasowang@redhat.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, martin.lau@linux.dev,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
mst@redhat.com, netdev@vger.kernel.org, parav@nvidia.com,
rostedt@goodmis.org, sdf@google.com, song@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] [trace?] possible deadlock in task_fork_fair
Date: Tue, 24 Dec 2024 22:55:02 -0800 [thread overview]
Message-ID: <676bac46.050a0220.2f3838.02c0.GAE@google.com> (raw)
In-Reply-To: <000000000000e7765006072e9591@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=16e922f8580000
start commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=aef2a55903e5791c
dashboard link: https://syzkaller.appspot.com/bug?extid=1a93ee5d329e97cfbaff
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128b2d33180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10fe01eb180000
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
next prev parent reply other threads:[~2024-12-25 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 6:28 [syzbot] [kernel?] possible deadlock in task_fork_fair syzbot
2023-12-12 1:01 ` [syzbot] [bpf?] [trace?] " syzbot
2023-12-12 12:26 ` syzbot
2024-12-25 6:55 ` syzbot [this message]
2025-10-14 14:07 ` Tetsuo Handa
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=676bac46.050a0220.2f3838.02c0.GAE@google.com \
--to=syzbot+1a93ee5d329e97cfbaff@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=elic@nvidia.com \
--cc=haoluo@google.com \
--cc=jakub@cloudflare.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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 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.