From: syzbot <syzbot+9765367bb86a19d38732@syzkaller.appspotmail.com>
To: anmol.karan123@gmail.com, dhowells@redhat.com,
dwmw2@infradead.org, jamie@nuviainc.com,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
lizhe67@huawei.com, richard@nod.at, sandeen@sandeen.net,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: general protection fault in jffs2_parse_param
Date: Sun, 17 Jan 2021 08:14:07 -0800 [thread overview]
Message-ID: <0000000000001b4eeb05b91ae518@google.com> (raw)
In-Reply-To: <000000000000418c7705afcff2e1@google.com>
syzbot suspects this issue was fixed by commit:
commit a61df3c413e49b0042f9caf774c58512d1cc71b7
Author: Jamie Iles <jamie@nuviainc.com>
Date: Mon Oct 12 13:12:04 2020 +0000
jffs2: Fix NULL pointer dereference in rp_size fs option parsing
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15cb91e7500000
start commit: bf3e7628 Merge branch 'mtd/fixes' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=61033507391c77ff
dashboard link: https://syzkaller.appspot.com/bug?extid=9765367bb86a19d38732
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d81f32500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13516852500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: jffs2: Fix NULL pointer dereference in rp_size fs option parsing
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-01-17 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 10:02 general protection fault in jffs2_parse_param syzbot
2021-01-17 16:14 ` syzbot [this message]
2021-01-25 9:36 ` Dmitry Vyukov
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=0000000000001b4eeb05b91ae518@google.com \
--to=syzbot+9765367bb86a19d38732@syzkaller.appspotmail.com \
--cc=anmol.karan123@gmail.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jamie@nuviainc.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lizhe67@huawei.com \
--cc=richard@nod.at \
--cc=sandeen@sandeen.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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