From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Ritesh Harjani <riteshh@linux.ibm.com>
Cc: syzbot <syzbot+9567fda428fba259deba@syzkaller.appspotmail.com>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Jan Kara <jack@suse.cz>
Subject: Re: general protection fault in ext4_writepages
Date: Mon, 11 Nov 2019 13:24:17 -0500 [thread overview]
Message-ID: <20191111182417.GB5165@mit.edu> (raw)
In-Reply-To: <20191111053231.F129B11C04C@d06av25.portsmouth.uk.ibm.com>
On Mon, Nov 11, 2019 at 11:02:31AM +0530, Ritesh Harjani wrote:
>
> Updating the link.
>
> On 11/11/19 10:42 AM, Ritesh Harjani wrote:
> > Hello Ted,
> >
> > This issue seems to be coming via fault injection failure in slab
> > allocation. This should be fixed via below patch on your latest ext4
> > branch.
> >
> > https://marc.info/?l=linux-ext4&m=804&w=2
> https://marc.info/?l=linux-ext4&m=157303310723804&w=2
Agreed, although unfortunately I wasn't able to make the reproducer
cause a failure _without_ the patch. Perhaps something other than
enabling FAILSLAB and KASAN was needed?
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git test
Let's see if the Syzbot can confirm that the patch addresses the problem.
- Ted
next prev parent reply other threads:[~2019-11-11 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 23:44 general protection fault in ext4_writepages syzbot
2019-11-11 5:12 ` Ritesh Harjani
2019-11-11 5:32 ` Ritesh Harjani
2019-11-11 18:24 ` Theodore Y. Ts'o [this message]
2019-11-11 19:25 ` syzbot
2019-11-19 3:16 ` Eric Biggers
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=20191111182417.GB5165@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=syzbot+9567fda428fba259deba@syzkaller.appspotmail.com \
--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).