From: syzbot <syzbot+3bd970a1887812621b4c@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
Subject: Re: [syzbot] [can?] possible deadlock in j1939_sk_queue_drop_all
Date: Wed, 13 Mar 2024 05:23:04 -0700 [thread overview]
Message-ID: <0000000000002755ce061389d67b@google.com> (raw)
In-Reply-To: <00000000000095640f05cb78af37@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=10e4d371180000
start commit: dd72f9c7e512 Merge tag 'spi-fix-v6-6-rc4' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=12abf4cc4f802b24
dashboard link: https://syzkaller.appspot.com/bug?extid=3bd970a1887812621b4c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17602089680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13398a9d680000
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-13 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 9:41 [syzbot] possible deadlock in j1939_sk_queue_drop_all syzbot
2022-06-03 19:14 ` syzbot
2024-03-13 12:23 ` syzbot [this message]
2024-03-13 13:59 ` [syzbot] [can?] " 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=0000000000002755ce061389d67b@google.com \
--to=syzbot+3bd970a1887812621b4c@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 \
/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).