From: syzbot <syzbot+feff46f1778030d14234@syzkaller.appspotmail.com>
To: bst@pengutronix.de, davem@davemloft.net,
dev.kurt@vandijck-laurijssen.be, ecathinds@gmail.com,
kernel@pengutronix.de, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@rempel-privat.de,
lkp@intel.com, maxime.jayat@mobile-devices.fr,
mkl@pengutronix.de, netdev@vger.kernel.org,
o.rempel@pengutronix.de, robin@protonic.nl,
socketcan@hartkopp.net, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in j1939_priv_get_by_ndev_locked
Date: Sun, 03 Nov 2019 01:04:00 -0700 [thread overview]
Message-ID: <00000000000050f87c05966ca43a@google.com> (raw)
In-Reply-To: <000000000000595be405966c3231@google.com>
syzbot has bisected this bug to:
commit 9d71dd0c70099914fcd063135da3c580865e924c
Author: The j1939 authors <linux-can@vger.kernel.org>
Date: Mon Oct 8 09:48:36 2018 +0000
can: add support of SAE J1939 protocol
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11267914e00000
start commit: 7de08690 powerpc/bpf: Fix tail call implementation
git tree: bpf
final crash: https://syzkaller.appspot.com/x/report.txt?x=13267914e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15267914e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2cc209e226c8fbbd
dashboard link: https://syzkaller.appspot.com/bug?extid=feff46f1778030d14234
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1726e97ce00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1678e4ece00000
Reported-by: syzbot+feff46f1778030d14234@syzkaller.appspotmail.com
Fixes: 9d71dd0c7009 ("can: add support of SAE J1939 protocol")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-03 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 7:32 general protection fault in j1939_priv_get_by_ndev_locked syzbot
2019-11-03 8:04 ` syzbot [this message]
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=00000000000050f87c05966ca43a@google.com \
--to=syzbot+feff46f1778030d14234@syzkaller.appspotmail.com \
--cc=bst@pengutronix.de \
--cc=davem@davemloft.net \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=ecathinds@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=lkp@intel.com \
--cc=maxime.jayat@mobile-devices.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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).