From: syzbot <syzbot+4857323ec1bb236f6a45@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_sk_bind
Date: Fri, 17 Jan 2020 01:06:01 -0800 [thread overview]
Message-ID: <0000000000002ab713059c524079@google.com> (raw)
In-Reply-To: <000000000000a367e3059691c6b4@google.com>
syzbot suspects this bug was fixed by commit:
commit 00d4e14d2e4caf5f7254a505fee5eeca8cd37bd4
Author: Oleksij Rempel <o.rempel@pengutronix.de>
Date: Fri Dec 6 14:18:35 2019 +0000
can: j1939: j1939_sk_bind(): take priv after lock is held
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1001b266e00000
start commit: 32ef9553 Merge tag 'fsnotify_for_v5.5-rc1' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c2e464ae414aee8c
dashboard link: https://syzkaller.appspot.com/bug?extid=4857323ec1bb236f6a45
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=177c34a2e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: can: j1939: j1939_sk_bind(): take priv after lock is held
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-01-17 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 4:22 general protection fault in j1939_sk_bind syzbot
2019-11-05 16:27 ` syzbot
2020-01-17 9:06 ` 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=0000000000002ab713059c524079@google.com \
--to=syzbot+4857323ec1bb236f6a45@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).