[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d9be3fbf-023c-ac55-5097-ea3f43a946b4@huawei.com>
Date: Sat, 3 Jun 2023 10:05:44 +0800
From: Baokun Li <libaokun1@...wei.com>
To: Theodore Ts'o <tytso@....edu>
CC: syzbot <syzbot+list5ea887c46d22b2acf805@...kaller.appspotmail.com>,
<adilger.kernel@...ger.ca>, <linux-ext4@...r.kernel.org>,
<linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<syzkaller-bugs@...glegroups.com>,
yangerkun <yangerkun@...wei.com>,
Baokun Li <libaokun1@...wei.com>
Subject: Re: [syzbot] Monthly ext4 report (May 2023)
On 2023/6/3 5:06, Theodore Ts'o wrote:
> On Thu, Jun 01, 2023 at 10:08:53AM +0800, Baokun Li wrote:
>> Patch "[PATCH v2] ext4: fix race condition between buffer write and
>> page_mkwrite"
>> in maillist fixes issues <1>,<4>,<5>.
>>
>> Patch set "[PATCH v4 00/12] ext4: fix WARNING in
>> ext4_da_update_reserve_space"
>> in maillist fixes issues <3>.
> Thanks for noting that the fixes are applicable to the above reports.
> I've adjusted the commit descrptions to include the necessary
> Reported-by: lines, and they are in the ext4 dev tree.
>
> Cheers,
>
> - Ted
>
Thank you very much for your Applied!
There are many sources of syzkaller issues, and the patches I send out
to fix syzkaller issues add Reported-by to all but the ones that fix issues
reported by our internal syzbot.
However, there may be multiple syzbot reports for the same issue.
So I sorry for not adding the "Reported-by:" for the corresponding issue
above.
Please feel free to give me your feedback if the patches have any problems.
Thanks! 😀
--
With Best Regards,
Baokun Li
.
Powered by blists - more mailing lists