From: syzbot <syzbot+6c5d567447bfa30f78e2@syzkaller.appspotmail.com>
To: adobriyan@gmail.com, akinobu.mita@gmail.com,
akpm@linux-foundation.org, ben@decadent.org.uk,
davem@davemloft.net, dvyukov@google.com,
linux-kernel@vger.kernel.org, mhocko@kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tejaswit@codeaurora.org, torvalds@linux-foundation.org
Subject: Re: BUG: unable to handle kernel paging request in slhc_free
Date: Thu, 05 Dec 2019 12:26:00 -0800 [thread overview]
Message-ID: <000000000000cf2c140598fabc5c@google.com> (raw)
In-Reply-To: <000000000000675cea057e201cbb@google.com>
syzbot suspects this bug was fixed by commit:
commit baf76f0c58aec435a3a864075b8f6d8ee5d1f17e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu Apr 25 23:13:58 2019 +0000
slip: make slhc_free() silently accept an error pointer
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=114af97ee00000
start commit: 8fe28cb5 Linux 4.20
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7d581260bae0899a
dashboard link: https://syzkaller.appspot.com/bug?extid=6c5d567447bfa30f78e2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136130fd400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1607c563400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: slip: make slhc_free() silently accept an error pointer
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-05 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 2:41 BUG: unable to handle kernel paging request in slhc_free syzbot
2019-03-16 14:49 ` syzbot
2019-03-16 17:24 ` Linus Torvalds
2019-11-16 17:42 ` syzbot
2019-12-05 20:26 ` 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=000000000000cf2c140598fabc5c@google.com \
--to=syzbot+6c5d567447bfa30f78e2@syzkaller.appspotmail.com \
--cc=adobriyan@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tejaswit@codeaurora.org \
--cc=torvalds@linux-foundation.org \
/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.