From: Andrew Morton <akpm@linux-foundation.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
syzkaller-bugs@googlegroups.com
Subject: Re: Please drop 64d9183203eeb in mm-nonmm-unstable ([syzbot] [exfat?] WARNING in fat_ent_write)
Date: Mon, 24 Aug 2026 09:50:13 -0700 [thread overview]
Message-ID: <20260824095013.ec38b9d5d5ec33922aad47e2@linux-foundation.org> (raw)
In-Reply-To: <875x0z6f0u.fsf@mail.parknet.co.jp>
On Mon, 24 Aug 2026 18:31:29 +0900 OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/fs/fat/misc.c?h=mm-nonmm-unstable&id=64d9183203eebe33de6188b70a8c1e91f52885db (fat: restore original value when fat_ent_write failed)
>
> This commit was missing to consider about the path of error by sync
> write. Since current bh write clears uptodate flag if got I/O error, so
> this patch doesn't work for now with wait==true.
>
> Please drop this patch at least until stop clearing the uptodate by bh
> sync write and buffer is reusable after the error.
This is now in Linus's tree, as 64d9183203ee. Please send along a fix,
with
Fixes: 64d9183203ee ("fat: restore original value when fat_ent_write failed")
next prev parent reply other threads:[~2026-08-24 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 7:47 [syzbot] [exfat?] WARNING in fat_ent_write syzbot
2026-08-24 9:31 ` Please drop 64d9183203eeb in mm-nonmm-unstable ([syzbot] [exfat?] WARNING in fat_ent_write) OGAWA Hirofumi
2026-08-24 16:50 ` Andrew Morton [this message]
2026-08-25 12:11 ` [PATCH] fat: Fix fat_ent_write() for reverting the value OGAWA Hirofumi
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=20260824095013.ec38b9d5d5ec33922aad47e2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.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.