From: syzbot <syzbot+f32cbede7fd867ce0d56@syzkaller.appspotmail.com>
To: astrajoan@yahoo.com, 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, o.rempel@pengutronix.de,
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: Thu, 14 Mar 2024 22:08:04 -0700 [thread overview]
Message-ID: <0000000000002d73880613abfe48@google.com> (raw)
In-Reply-To: <000000000000e8364c05ceefa4cf@google.com>
syzbot suspects this issue was fixed by commit:
commit 6cdedc18ba7b9dacc36466e27e3267d201948c8d
Author: Ziqi Zhao <astrajoan@yahoo.com>
Date: Fri Jul 21 16:22:26 2023 +0000
can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10c1afc1180000
start commit: 296455ade1fd Merge tag 'char-misc-6.8-rc1' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8e8eb82c088a8ac6
dashboard link: https://syzkaller.appspot.com/bug?extid=f32cbede7fd867ce0d56
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d7b3afe80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ba0a4fe80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-03-15 5:08 UTC|newest]
Thread overview: 6+ 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
2024-03-15 5:08 ` syzbot [this message]
2024-03-15 14:34 ` Oleksij Rempel
[not found] <20230709083511.1624-1-hdanton@sina.com>
2023-07-09 9:13 ` syzbot
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=0000000000002d73880613abfe48@google.com \
--to=syzbot+f32cbede7fd867ce0d56@syzkaller.appspotmail.com \
--cc=astrajoan@yahoo.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=o.rempel@pengutronix.de \
--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 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.