From: syzbot <syzbot+fa379358c28cc87cc307@syzkaller.appspotmail.com>
To: axboe@kernel.dk, davem@davemloft.net, edumazet@google.com,
hdanton@sina.com, horms@kernel.org, kuba@kernel.org,
kuni1840@gmail.com, kuniyu@amazon.com,
linux-kernel@vger.kernel.org, mhal@rbox.co,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] possible deadlock in __unix_gc
Date: Tue, 23 Apr 2024 19:01:03 -0700 [thread overview]
Message-ID: <000000000000f450900616ce0aa5@google.com> (raw)
In-Reply-To: <000000000000f1761a0616c5c629@google.com>
syzbot has bisected this issue to:
commit 47d8ac011fe1c9251070e1bd64cb10b48193ec51
Author: Michal Luczaj <mhal@rbox.co>
Date: Tue Apr 9 20:09:39 2024 +0000
af_unix: Fix garbage collector racing against connect()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f440d3180000
start commit: 4d2008430ce8 Merge tag 'docs-6.9-fixes2' of git://git.lwn...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=100c40d3180000
console output: https://syzkaller.appspot.com/x/log.txt?x=17f440d3180000
kernel config: https://syzkaller.appspot.com/x/.config?x=98d5a8e00ed1044a
dashboard link: https://syzkaller.appspot.com/bug?extid=fa379358c28cc87cc307
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a8fb4f180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ceeb73180000
Reported-by: syzbot+fa379358c28cc87cc307@syzkaller.appspotmail.com
Fixes: 47d8ac011fe1 ("af_unix: Fix garbage collector racing against connect()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-04-24 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 16:09 [syzbot] [net?] possible deadlock in __unix_gc syzbot
2024-04-24 0:43 ` Kuniyuki Iwashima
2024-04-24 1:11 ` syzbot
2024-04-24 2:01 ` 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=000000000000f450900616ce0aa5@google.com \
--to=syzbot+fa379358c28cc87cc307@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.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 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).