From: syzbot <syzbot+e227429f6fa77945d7e4@syzkaller.appspotmail.com>
To: alibuda@linux.alibaba.com, davem@davemloft.net,
dsahern@kernel.org, dust.li@linux.alibaba.com,
edumazet@google.com, horms@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, schnelle@linux.ibm.com,
syzkaller-bugs@googlegroups.com, wenjia@linux.ibm.com
Subject: Re: [syzbot] [net?] possible deadlock in ip_mroute_setsockopt
Date: Mon, 25 Nov 2024 03:30:02 -0800 [thread overview]
Message-ID: <67445fba.050a0220.1cc393.0078.GAE@google.com> (raw)
In-Reply-To: <00000000000009ff2e061ce633d7@google.com>
syzbot has bisected this issue to:
commit d25a92ccae6bed02327b63d138e12e7806830f78
Author: D. Wythe <alibuda@linux.alibaba.com>
Date: Thu Jun 13 18:00:30 2024 +0000
net/smc: Introduce IPPROTO_SMC
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15fc6530580000
start commit: fcc79e1714e8 Merge tag 'net-next-6.13' of git://git.kernel..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17fc6530580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13fc6530580000
kernel config: https://syzkaller.appspot.com/x/.config?x=275de99a754927af
dashboard link: https://syzkaller.appspot.com/bug?extid=e227429f6fa77945d7e4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=175459c0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10dc0ee8580000
Reported-by: syzbot+e227429f6fa77945d7e4@syzkaller.appspotmail.com
Fixes: d25a92ccae6b ("net/smc: Introduce IPPROTO_SMC")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-11-25 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 15:21 [syzbot] [net?] possible deadlock in ip_mroute_setsockopt syzbot
2024-11-24 23:45 ` syzbot
2024-11-25 11:30 ` 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=67445fba.050a0220.1cc393.0078.GAE@google.com \
--to=syzbot+e227429f6fa77945d7e4@syzkaller.appspotmail.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=schnelle@linux.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wenjia@linux.ibm.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