public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Baokun Li <libaokun1@huawei.com>
To: 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>, <tytso@mit.edu>
Cc: Baokun Li <libaokun1@huawei.com>, yangerkun <yangerkun@huawei.com>
Subject: Re: [syzbot] Monthly ext4 report (May 2023)
Date: Thu, 1 Jun 2023 10:08:53 +0800	[thread overview]
Message-ID: <df5e7e7d-875c-8e5d-1423-82ec58299b1b@huawei.com> (raw)
In-Reply-To: <000000000000834af205fce87c00@google.com>

On 2023/5/30 20:38, syzbot wrote:
> Hello ext4 maintainers/developers,
>
> This is a 31-day syzbot report for the ext4 subsystem.
> All related reports/information can be found at:
> https://syzkaller.appspot.com/upstream/s/ext4
>
> During the period, 3 new issues were detected and 10 were fixed.
> In total, 46 issues are still open and 106 have been fixed so far.
>
> Some of the still happening issues:
>
> Ref Crashes Repro Title
> <1> 124     Yes   kernel BUG in ext4_do_writepages
>                    https://syzkaller.appspot.com/bug?extid=d1da16f03614058fdc48
> <2> 48      No    WARNING in ext4_write_inode (2)
>                    https://syzkaller.appspot.com/bug?extid=748cc361874fca7d33cc
> <3> 8       Yes   WARNING in ext4_da_update_reserve_space (2)
>                    https://syzkaller.appspot.com/bug?extid=a1232eabd7a3d43d4fb5
> <4> 8       Yes   kernel BUG in __ext4_journal_stop
>                    https://syzkaller.appspot.com/bug?extid=bdab24d5bf96d57c50b0
> <5> 7       Yes   kernel BUG in ext4_write_inline_data
>                    https://syzkaller.appspot.com/bug?extid=f4582777a19ec422b517
>
> ---
>

Hello, Theodore!

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>.

These patches have been reviewed, could you have time to merge them in?
I would appreciate it if you could.

Thanks!
-- 
With Best Regards,
Baokun Li
.

  reply	other threads:[~2023-06-01  2:09 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 [this message]
2023-06-02 21:06   ` Theodore Ts'o
2023-06-03  2:05     ` Baokun Li
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=df5e7e7d-875c-8e5d-1423-82ec58299b1b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox