[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <77DB8D1D-4650-4A4C-BAE0-B04C29A06E20@gmail.com>
Date: Thu, 16 May 2024 13:42:00 -0400
From: Shuangpeng Bai <shuangpengbai@...il.com>
To: Dmitry Vyukov <dvyukov@...gle.com>,
Theodore Ts'o <tytso@....edu>
Cc: linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org,
syzkaller@...glegroups.com
Subject: Re: KASAN: use-after-free in ext4_find_extent in v6.9
I will follow the suggestions. Thank you!
> On May 16, 2024, at 10:44, Dmitry Vyukov <dvyukov@...gle.com> wrote:
>
> On Thu, 16 May 2024 at 15:58, Theodore Ts'o <tytso@....edu> wrote:
>>
>> 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.
>
> FWIW we provide configs used by syzbot here (upstream-*):
> https://github.com/google/syzkaller/tree/master/dashboard/config/linux
>
> + a bunch of configs fragments with explanations why things are
> enabled/disabled:
> https://github.com/google/syzkaller/blob/master/dashboard/config/linux/bits/maintained.yml
> https://github.com/google/syzkaller/blob/master/dashboard/config/linux/bits/base.yml
> https://github.com/google/syzkaller/blob/master/dashboard/config/linux/bits/debug.yml
Powered by blists - more mailing lists