From: syzbot <syzbot+f32cbede7fd867ce0d56@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
kernel@pengutronix.de, kuba@kernel.org,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@rempel-privat.de, mkl@pengutronix.de,
netdev@vger.kernel.org, pabeni@redhat.com, robin@protonic.nl,
socketcan@hartkopp.net, syzkaller-bugs@googlegroups.com,
wg@grandegger.com
Subject: Re: [syzbot] [can?] possible deadlock in j1939_session_activate
Date: Tue, 24 Oct 2023 23:02:31 -0700 [thread overview]
Message-ID: <0000000000006a55890608843368@google.com> (raw)
In-Reply-To: <000000000000e8364c05ceefa4cf@google.com>
syzbot has bisected this issue to:
commit 259bdba27e32368b4404f69d613b1c1014c07cbf
Author: Oliver Hartkopp <socketcan@hartkopp.net>
Date: Wed Mar 9 12:04:16 2022 +0000
vxcan: enable local echo for sent CAN frames
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14a2e55d680000
start commit: 84186fcb834e Merge tag 'urgent/nolibc.2023.10.16a' of git:..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16a2e55d680000
console output: https://syzkaller.appspot.com/x/log.txt?x=12a2e55d680000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d1f30869bb78ec6
dashboard link: https://syzkaller.appspot.com/bug?extid=f32cbede7fd867ce0d56
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c6300d680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e6935d680000
Reported-by: syzbot+f32cbede7fd867ce0d56@syzkaller.appspotmail.com
Fixes: 259bdba27e32 ("vxcan: enable local echo for sent CAN frames")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-10-25 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 11:52 [syzbot] possible deadlock in j1939_session_activate syzbot
2023-07-09 3:11 ` [syzbot] [can?] " syzbot
2023-10-25 6:02 ` syzbot [this message]
2024-03-15 5:08 ` syzbot
2024-03-15 14:34 ` Oleksij Rempel
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=0000000000006a55890608843368@google.com \
--to=syzbot+f32cbede7fd867ce0d56@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wg@grandegger.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).