From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Dmitry Antipov <dmantipov@yandex.ru>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: syzbot+803dd716c4310d16ff3a@syzkaller.appspotmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] fs: f2fs: end all corrupted fs writes with -EFSCORRUPTED
Date: Fri, 25 Apr 2025 10:29:06 +0800 [thread overview]
Message-ID: <55c493aa-c015-470f-bdcc-e625ba17a131@kernel.org> (raw)
In-Reply-To: <20250423161527.152834-1-dmantipov@yandex.ru>
On 4/24/25 00:15, Dmitry Antipov wrote:
> In 'f2fs_write_end_io()', end all of the in-progress writes with
> -EFSCORRUPTED if the corresponding error was detected earlier.
>
> Reported-by: syzbot+803dd716c4310d16ff3a@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=803dd716c4310d16ff3a
> Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
> ---
> fs/f2fs/data.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 54f89f0ee69b..755806868f0e 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -320,9 +320,11 @@ static void f2fs_write_end_io(struct bio *bio)
> {
> struct f2fs_sb_info *sbi;
> struct folio_iter fi;
> + bool check;
>
> iostat_update_and_unbind_ctx(bio);
> sbi = bio->bi_private;
> + check = is_sbi_flag_set(sbi, SBI_NEED_FSCK);
>
> if (time_to_inject(sbi, FAULT_WRITE_IO))
> bio->bi_status = BLK_STS_IOERR;
> @@ -331,6 +333,11 @@ static void f2fs_write_end_io(struct bio *bio)
> struct folio *folio = fi.folio;
> enum count_type type;
>
> + if (check) {
> + mapping_set_error(folio->mapping, -EFSCORRUPTED);
> + continue;
Backing to the implementation, it seems it won't release resources
below, e.g. missed to call:
- fscrypt_free_bounce_page()
- f2fs_compress_write_end_io()
...
- folio_end_writeback()
I guess it may hang kernel w/ this patch? Or any thing I missed?
Thanks,
> + }
> +
> if (fscrypt_is_bounce_folio(folio)) {
> struct folio *io_folio = folio;
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-04-25 2:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 16:15 [f2fs-dev] [PATCH] fs: f2fs: end all corrupted fs writes with -EFSCORRUPTED Dmitry Antipov
2025-04-24 8:58 ` Chao Yu via Linux-f2fs-devel
2025-04-24 10:43 ` Dmitry Antipov
2025-04-25 2:52 ` Chao Yu via Linux-f2fs-devel
2025-04-25 2:29 ` Chao Yu via Linux-f2fs-devel [this message]
2025-08-11 10:00 ` Chao Yu via Linux-f2fs-devel
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=55c493aa-c015-470f-bdcc-e625ba17a131@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=jaegeuk@kernel.org \
--cc=syzbot+803dd716c4310d16ff3a@syzkaller.appspotmail.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.