From: syzbot <syzbot+1591462f226d9cbf0564@syzkaller.appspotmail.com>
To: arnd@arndb.de, astrajoan@yahoo.com,
bridge@lists.linux-foundation.org, davem@davemloft.net,
dvyukov@google.com, edumazet@google.com, hdanton@sina.com,
ivan.orlov0322@gmail.com, kernel@pengutronix.de,
kuba@kernel.org, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@rempel-privat.de,
mkl@pengutronix.de, mudongliangabcd@gmail.com,
netdev@vger.kernel.org, nikolay@nvidia.com,
o.rempel@pengutronix.de, pabeni@redhat.com, robin@protonic.nl,
roopa@nvidia.com, skhan@linuxfoundation.org,
socketcan@hartkopp.net, stephen@networkplumber.org,
syzkaller-bugs@googlegroups.com, syzkaller@googlegroups.com
Subject: Re: [syzbot] [can?] possible deadlock in j1939_sk_errqueue (2)
Date: Tue, 14 Nov 2023 19:54:05 -0800 [thread overview]
Message-ID: <000000000000cb9c3d060a28dad8@google.com> (raw)
In-Reply-To: <0000000000008981d905ffa345de@google.com>
syzbot has bisected this issue to:
commit 2030043e616cab40f510299f09b636285e0a3678
Author: Oleksij Rempel <o.rempel@pengutronix.de>
Date: Fri May 21 11:57:20 2021 +0000
can: j1939: fix Use-after-Free, hold skb ref while in use
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1438c947680000
start commit: 1b907d050735 Merge tag '6.7-rc-smb3-client-fixes-part2' of..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1638c947680000
console output: https://syzkaller.appspot.com/x/log.txt?x=1238c947680000
kernel config: https://syzkaller.appspot.com/x/.config?x=88e7ba51eecd9cd6
dashboard link: https://syzkaller.appspot.com/bug?extid=1591462f226d9cbf0564
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17fea8fb680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1633dc70e80000
Reported-by: syzbot+1591462f226d9cbf0564@syzkaller.appspotmail.com
Fixes: 2030043e616c ("can: j1939: fix Use-after-Free, hold skb ref while in use")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-15 3:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 6:19 [syzbot] [can?] possible deadlock in j1939_sk_errqueue (2) syzbot
2023-07-04 6:47 ` [PATCH] can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock Ziqi Zhao
2023-07-04 6:47 ` syzbot
2023-07-04 7:37 ` Oleksij Rempel
2023-07-21 16:22 ` [Bridge] " Ziqi Zhao
2023-07-21 16:22 ` Ziqi Zhao
2023-07-23 15:41 ` [Bridge] " Oleksij Rempel
2023-07-23 15:41 ` Oleksij Rempel
2023-08-07 4:46 ` [Bridge] " Oleksij Rempel
2023-08-07 4:46 ` Oleksij Rempel
2023-11-17 8:10 ` Oleksij Rempel
2023-07-10 17:53 ` [syzbot] [can?] possible deadlock in j1939_sk_errqueue (2) syzbot
2023-07-12 0:47 ` [PATCH] can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock Ziqi Zhao
2023-07-12 1:16 ` [syzbot] [can?] possible deadlock in j1939_sk_errqueue (2) syzbot
2023-07-13 22:23 ` [PATCH] can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock Stephen Hemminger
2023-11-15 3:54 ` syzbot [this message]
[not found] <20230711131958.334-1-hdanton@sina.com>
2023-07-11 13:20 ` [syzbot] [can?] possible deadlock in j1939_sk_errqueue (2) syzbot
2023-07-11 13:47 ` 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=000000000000cb9c3d060a28dad8@google.com \
--to=syzbot+1591462f226d9cbf0564@syzkaller.appspotmail.com \
--cc=arnd@arndb.de \
--cc=astrajoan@yahoo.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=ivan.orlov0322@gmail.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=mudongliangabcd@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robin@protonic.nl \
--cc=roopa@nvidia.com \
--cc=skhan@linuxfoundation.org \
--cc=socketcan@hartkopp.net \
--cc=stephen@networkplumber.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@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 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.