From: "Theodore Ts'o" <tytso@mit.edu>
To: yebin <yebin10@huawei.com>
Cc: Eric Whitney <enwlinux@gmail.com>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH -next] ext4: Fix warning in ext4_da_release_space
Date: Fri, 27 May 2022 11:21:44 -0400 [thread overview]
Message-ID: <YpDsiCTi8sidvO7X@mit.edu> (raw)
In-Reply-To: <62909593.2040809@huawei.com>
On Fri, May 27, 2022 at 05:10:43PM +0800, yebin wrote:
>
> Maybe you can run syzkaller with log as follows :
Oh, so this was something that was found using Syzkaller. Was this
using the public syzkaller; if so, can you provide a link the
Syzkaller report?
If this was a from privately run syzkaller instance, was there a C
reproducer? It appears that this was from a fuzzed instance, and it's
painful enoguh to extract the file system image from the C reproducer.
I have no idea how to extract the file system image from a Syzkaller
reproducer.
In any case, it sounds like this was triggered from a maliciously
corrupted / fuzzed image. Can this warning be triggered from a
consistent file system, or does it require a corrupted extent tree?
- Ted
next prev parent reply other threads:[~2022-05-27 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 2:55 [PATCH -next] ext4: Fix warning in ext4_da_release_space Ye Bin
2022-05-26 19:55 ` Eric Whitney
[not found] ` <62909593.2040809@huawei.com>
2022-05-27 15:21 ` Theodore Ts'o [this message]
2022-06-13 7:16 ` yebin
2022-06-15 0:53 ` Eric Whitney
2022-06-15 4:03 ` yebin
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=YpDsiCTi8sidvO7X@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=enwlinux@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yebin10@huawei.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).