From: Eric Biggers <ebiggers@kernel.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
syzbot+f8d6f8386ceacdbfff57@syzkaller.appspotmail.com,
stable@kernel.org
Subject: Re: [PATCH -v2] ext4: add more paranoia checking in ext4_expand_extra_isize handling
Date: Mon, 18 Nov 2019 20:36:40 -0800 [thread overview]
Message-ID: <20191119043640.GE163020@sol.localdomain> (raw)
In-Reply-To: <20191119042120.GD4262@mit.edu>
On Mon, Nov 18, 2019 at 11:21:20PM -0500, Theodore Y. Ts'o wrote:
> On Mon, Nov 18, 2019 at 06:15:26PM -0800, Eric Biggers wrote:
> > Is this patch intended to address
> > https://lore.kernel.org/linux-ext4/000000000000950f21059564e4c7@google.com
> > as well? If so, you can add the second Reported-by line so that both syzbot
> > reports get closed.
>
> Yes, it appears to be the same issue. Thanks for pointing this out!
>
> - Ted
There's actually a third that looks very similar too:
"KASAN: use-after-free Write in __ext4_expand_extra_isize (2)"
https://lkml.kernel.org/linux-ext4/0000000000000d74c7059564e17f@google.com/
If these are all fixed by this patch, you can use:
Reported-by: syzbot+f8d6f8386ceacdbfff57@syzkaller.appspotmail.com
Reported-by: syzbot+33d7ea72e47de3bdf4e1@syzkaller.appspotmail.com
Reported-by: syzbot+44b6763edfc17144296f@syzkaller.appspotmail.com
prev parent reply other threads:[~2019-11-19 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 2:48 [PATCH] ext4: add more paranoia checking in ext4_expand_extra_isize handling Theodore Ts'o
2019-11-10 10:12 ` kbuild test robot
2019-11-10 12:15 ` [PATCH -v2] " Theodore Y. Ts'o
2019-11-19 2:15 ` Eric Biggers
2019-11-19 4:21 ` Theodore Y. Ts'o
2019-11-19 4:36 ` Eric Biggers [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=20191119043640.GE163020@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=lkp@intel.com \
--cc=stable@kernel.org \
--cc=syzbot+f8d6f8386ceacdbfff57@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
/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).