From: Baokun Li <libaokun1@huawei.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: syzbot
<syzbot+list5ea887c46d22b2acf805@syzkaller.appspotmail.com>,
<adilger.kernel@dilger.ca>, <linux-ext4@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<syzkaller-bugs@googlegroups.com>,
yangerkun <yangerkun@huawei.com>,
Baokun Li <libaokun1@huawei.com>
Subject: Re: [syzbot] Monthly ext4 report (May 2023)
Date: Sat, 3 Jun 2023 10:05:44 +0800 [thread overview]
Message-ID: <d9be3fbf-023c-ac55-5097-ea3f43a946b4@huawei.com> (raw)
In-Reply-To: <20230602210639.GA1154817@mit.edu>
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
.
next prev parent reply other threads:[~2023-06-03 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 12:38 [syzbot] Monthly ext4 report (May 2023) syzbot
2023-06-01 2:08 ` Baokun Li
2023-06-02 21:06 ` Theodore Ts'o
2023-06-03 2:05 ` Baokun Li [this message]
2023-06-03 4:30 ` Theodore Ts'o
2023-06-03 6:20 ` Baokun Li
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=d9be3fbf-023c-ac55-5097-ea3f43a946b4@huawei.com \
--to=libaokun1@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+list5ea887c46d22b2acf805@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=yangerkun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.