From: syzbot <syzbot+535e5aae63c0d0433473@syzkaller.appspotmail.com>
To: davem@davemloft.net, idosch@nvidia.com, jacob.e.keller@intel.com,
jiri@nvidia.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
Subject: Re: [syzbot] [can?] WARNING in j1939_session_deactivate
Date: Wed, 03 May 2023 16:51:20 -0700 [thread overview]
Message-ID: <000000000000991adc05fad2bb84@google.com> (raw)
In-Reply-To: <00000000000065fe6705cad8850e@google.com>
syzbot suspects this issue was fixed by commit:
commit b20b8aec6ffc07bb547966b356780cd344f20f5b
Author: Ido Schimmel <idosch@nvidia.com>
Date: Wed Feb 15 07:31:39 2023 +0000
devlink: Fix netdev notifier chain corruption
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=120779c4280000
start commit: 7cd8b1542a7b ptp_pch: Load module automatically if ID matc..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=9290a409049988d4
dashboard link: https://syzkaller.appspot.com/bug?extid=535e5aae63c0d0433473
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1488b8e0b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14eabe3f300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: devlink: Fix netdev notifier chain corruption
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-05-03 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 10:36 [syzbot] WARNING in j1939_session_deactivate syzbot
2023-05-03 23:51 ` syzbot [this message]
2024-01-30 13:59 ` [syzbot] " 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=000000000000991adc05fad2bb84@google.com \
--to=syzbot+535e5aae63c0d0433473@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.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 \
/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.