From: "Theodore Ts'o" <tytso@mit.edu>
To: Shuangpeng Bai <shuangpengbai@gmail.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller@googlegroups.com
Subject: Re: KASAN: use-after-free in ext4_find_extent in v6.9
Date: Thu, 16 May 2024 07:58:21 -0600 [thread overview]
Message-ID: <20240516135821.GA272071@mit.edu> (raw)
In-Reply-To: <2184C9DB-DDC2-484B-A1B2-A1E312B62D54@gmail.com>
On Wed, May 15, 2024 at 08:33:33PM -0400, Shuangpeng Bai wrote:
>
> You are right. I disabled CONFIG_BLK_DEV_WRITE_MOUNTED and found
> this bug can not be triggered anymore.
>
> I am wondering if there is any suggested way for me to check whether
> a bug is reproduced under a reasonable environment (such as
> compiling config) or not? If so, that would be very helpful.
As I mentioned, the upstream syzkaller always forces the
CONFIG_BLK_DEV_WRITE_MOUNTED to be disabled. That's the best way to
check whether the bug is reproducible under a reasonable environment,
and to do it in an automated way.
Cheers,
- Ted
next prev parent reply other threads:[~2024-05-16 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 0:40 KASAN: use-after-free in ext4_find_extent in v6.9 Shuangpeng Bai
2024-05-15 22:49 ` Theodore Ts'o
2024-05-16 0:33 ` Shuangpeng Bai
2024-05-16 13:58 ` Theodore Ts'o [this message]
2024-05-16 14:44 ` Dmitry Vyukov
2024-05-16 17:42 ` Shuangpeng Bai
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=20240516135821.GA272071@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuangpengbai@gmail.com \
--cc=syzkaller@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