From: YangWen <anmuxixixi@gmail.com>
To: hirofumi@mail.parknet.co.jp
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fat: fix data-race between fat12_ent_put() and fat_mirror_bhs()
Date: Tue, 2 Sep 2025 22:20:44 +0800 [thread overview]
Message-ID: <20250902142044.9815-1-anmuxixixi@gmail.com> (raw)
In-Reply-To: <87ecsp0yar.fsf@mail.parknet.co.jp>
Hi,
OGAWA Hirofumi wrote:
> You are forgetting what I said first. I said, this should be temporary
> inconsistent. When unmount, temporary inconsistent should be fixed by
> later write out.
>
> IOW, I can't see why you claim this race can be the cause of permanent
> inconsistent.
I don’t have a reproducer showing a permanent corruption
after a clean unmount. My concern came only from KCSAN reports under
syzkaller, and then I tried to reason from the code.
In particular, in fat_mirror_bhs() there is a path:
if (sb->s_flags & SB_SYNCHRONOUS)
err = sync_dirty_buffer(c_bh);
So with -o sync mount, if memcpy() observes a half-updated FAT12 entry,
the torn value in the backup FAT buffer could be immediately written to
disk. In that case, even though the primary FAT is later corrected, the
backup FAT might persist inconsistent content.
Thanks.
next prev parent reply other threads:[~2025-09-02 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 8:17 YangWen
2025-09-02 9:01 ` OGAWA Hirofumi
2025-09-02 12:07 ` [PATCH] drivers: example: fix memory leak YangWen
2025-09-02 12:38 ` OGAWA Hirofumi
2025-09-02 13:24 ` [PATCH] fat: fix data-race between fat12_ent_put() and fat_mirror_bhs() YangWen
2025-09-02 13:38 ` OGAWA Hirofumi
2025-09-02 14:20 ` YangWen [this message]
2025-09-02 18:05 ` OGAWA Hirofumi
2025-09-03 2:28 ` YangWen
2025-09-02 12:11 ` YangWen
2025-09-02 19:56 ` kernel test robot
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=20250902142044.9815-1-anmuxixixi@gmail.com \
--to=anmuxixixi@gmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®