From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Edward Adam Davis <eadavis@qq.com>
Cc: linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
syzbot+d3c29ed63db6ddf8406e@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [PATCH V2] fat: Prevent the race of read/write the FAT32 entry
Date: Tue, 29 Jul 2025 18:03:51 +0900 [thread overview]
Message-ID: <87tt2v4bd4.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <tencent_24D0464B099CEEC72EFD4C95A7FB86DB9206@qq.com>
Edward Adam Davis <eadavis@qq.com> writes:
> syzbot reports data-race in fat32_ent_get/fat32_ent_put.
>
> CPU0(Task A) CPU1(Task B)
> ==== ====
> vfs_write
> new_sync_write
> generic_file_write_iter
> fat_write_begin
> block_write_begin vfs_statfs
> fat_get_block statfs_by_dentry
> fat_add_cluster fat_statfs
> fat_ent_write fat_count_free_clusters
> fat32_ent_put fat32_ent_get
>
> Task A's write operation on CPU0 and Task B's read operation on CPU1 occur
> simultaneously, generating an race condition.
>
> Add READ/WRITE_ONCE to solve the race condition that occurs when accessing
> FAT32 entry.
I mentioned about READ/WRITE_ONCE though, it was about possibility. Do
we really need to add those? Can you clarify more?
> diff --git a/fs/fat/fatent.c b/fs/fat/fatent.c
> index 1db348f8f887..a9eecd090d91 100644
> --- a/fs/fat/fatent.c
> +++ b/fs/fat/fatent.c
> @@ -146,8 +146,8 @@ static int fat16_ent_get(struct fat_entry *fatent)
>
> static int fat32_ent_get(struct fat_entry *fatent)
> {
> - int next = le32_to_cpu(*fatent->u.ent32_p) & 0x0fffffff;
> - WARN_ON((unsigned long)fatent->u.ent32_p & (4 - 1));
> + int next = le32_to_cpu(READ_ONCE(*fatent->u.ent32_p)) & 0x0fffffff;
> + WARN_ON((unsigned long)READ_ONCE(fatent->u.ent32_p) & (4 - 1));
Adding READ_ONCE() for pointer is broken.
> if (next >= BAD_FAT32)
> next = FAT_ENT_EOF;
> return next;
> @@ -187,8 +187,8 @@ static void fat16_ent_put(struct fat_entry *fatent, int new)
> static void fat32_ent_put(struct fat_entry *fatent, int new)
> {
> WARN_ON(new & 0xf0000000);
> - new |= le32_to_cpu(*fatent->u.ent32_p) & ~0x0fffffff;
> - *fatent->u.ent32_p = cpu_to_le32(new);
> + new |= le32_to_cpu(READ_ONCE(*fatent->u.ent32_p)) & ~0x0fffffff;
> + WRITE_ONCE(*fatent->u.ent32_p, cpu_to_le32(new));
> mark_buffer_dirty_inode(fatent->bhs[0], fatent->fat_inode);
> }
Also READ_ONCE() is really required here?
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2025-07-29 9:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 8:17 [syzbot] [exfat?] KCSAN: data-race in fat32_ent_get / fat32_ent_put syzbot
2025-07-28 11:37 ` [PATCH] fat: Prevent the race of read/write the FAT16 and FAT32 entry Edward Adam Davis
2025-07-28 15:10 ` OGAWA Hirofumi
2025-07-29 3:57 ` Edward Adam Davis
2025-07-28 16:04 ` Al Viro
2025-07-28 16:35 ` Al Viro
2025-07-29 4:17 ` Edward Adam Davis
2025-07-29 4:53 ` Al Viro
2025-07-29 5:04 ` Al Viro
2025-07-29 5:32 ` Edward Adam Davis
2025-07-29 6:17 ` [PATCH V2] fat: Prevent the race of read/write the " Edward Adam Davis
2025-07-29 9:03 ` OGAWA Hirofumi [this message]
2025-07-29 9:35 ` Al Viro
2025-07-29 10:06 ` Al Viro
2025-08-18 13:58 ` Edward Adam Davis
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=87tt2v4bd4.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=eadavis@qq.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzbot+d3c29ed63db6ddf8406e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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