mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: 余昊铖 <3230100410@zju.edu.cn>
To: "Baokun Li" <libaokun1@huawei.com>
Cc: security@kernel.org, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] ext4: Fix KASAN use-after-free in ext4_find_extent
Date: Wed, 17 Dec 2025 23:22:21 +0800 (GMT+08:00)	[thread overview]
Message-ID: <2ef68a02.45e3e.19b2ce7b7a0.Coremail.3230100410@zju.edu.cn> (raw)
In-Reply-To: <3f5ec6d7-d291-4b37-8914-3b4347564e98@huawei.com>

Hi,

Sorry but I am a bit confused by your words. My original fuzz tesing already enabled CONFIG_BLK_DEV_WRITE_MOUNTED as in most major Linux distributions. 

So does a bug found when CONFIG_BLK_DEV_WRITE_MOUNTED is enabled still hold value for reporting? Should I enable or disable this configuration in my future fuzzing work?

Thanks,
Haocheng Yu

> > Hi,
> >
> > I have disabled CONFIG_BLK_DEV_WRITE_MOUNTED and spent some time trying to trigger the reported KASAN issues. And I found neither of the two bugs has been observed since. Is this issue still worth investigating?
> 
> That essentially confirms the issue is caused by bypassing the
> filesystem to write directly to the raw disk. This is a known
> issue and is quite tricky to solve.
> 
> You can work around this specific class of issues in your fuzz
> testing by enabling CONFIG_BLK_DEV_WRITE_MOUNTED. Syzbot runs
> with this configuration enabled by default.
> 
> 
> Cheers,
> Baokun

  reply	other threads:[~2025-12-17 15:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09 12:27 余昊铖
2025-12-14  3:17 ` Theodore Tso
2025-12-14  8:52   ` 余昊铖
2025-12-15  1:54 ` Baokun Li
2025-12-15 11:11   ` 余昊铖
2025-12-15 12:42     ` Baokun Li
2025-12-17 15:22       ` 余昊铖 [this message]
2025-12-18  1:49         ` Baokun Li
2025-12-18  5:42           ` 余昊铖

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=2ef68a02.45e3e.19b2ce7b7a0.Coremail.3230100410@zju.edu.cn \
    --to=3230100410@zju.edu.cn \
    --cc=libaokun1@huawei.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    /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

all inboxes | Powered by JetHome®