From: syzbot <syzbot+3950016bd95c2ca0377b@syzkaller.appspotmail.com>
To: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
b.zolnierkie@samsung.com, davem@davemloft.net,
dri-devel@lists.freedesktop.org, kuba@kernel.org,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sctp@vger.kernel.org, lkundrak@v3.sk,
marcelo.leitner@gmail.com, mareklindner@neomailbox.ch,
netdev@vger.kernel.org, nhorman@tuxdriver.com,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
vyasevich@gmail.com
Subject: Re: general protection fault in sctp_ulpevent_nofity_peer_addr_change
Date: Fri, 20 Mar 2020 00:48:02 +0000 [thread overview]
Message-ID: <00000000000041ca9305a13ea3e0@google.com> (raw)
In-Reply-To: <00000000000074219d05a139e082@google.com>
syzbot has bisected this bug to:
commit da2648390ce3d409218b6bbbf2386d8ddeec2265
Author: Lubomir Rintel <lkundrak@v3.sk>
Date: Thu Dec 20 18:13:09 2018 +0000
pxa168fb: trivial typo fix
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x\x1361e139e00000
start commit: 5076190d mm: slub: be more careful about the double cmpxch..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x\x10e1e139e00000
console output: https://syzkaller.appspot.com/x/log.txt?x\x1761e139e00000
kernel config: https://syzkaller.appspot.com/x/.config?xŸ894bd92023de02
dashboard link: https://syzkaller.appspot.com/bug?extid950016bd95c2ca0377b
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x1162bbe3e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x\x13c93b45e00000
Reported-by: syzbot+3950016bd95c2ca0377b@syzkaller.appspotmail.com
Fixes: da2648390ce3 ("pxa168fb: trivial typo fix")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2020-03-20 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000074219d05a139e082@google.com>
2020-03-20 0:48 ` syzbot [this message]
2020-03-20 1:17 ` general protection fault in sctp_ulpevent_nofity_peer_addr_change Marcelo Ricardo Leitner
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=00000000000041ca9305a13ea3e0@google.com \
--to=syzbot+3950016bd95c2ca0377b@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=b.zolnierkie@samsung.com \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=kuba@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=marcelo.leitner@gmail.com \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.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).