From: Brian Foster <bfoster@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: lu gu <giveme.gulu@gmail.com>,
Joanne Koong <joannelkoong@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Bernd Schubert <bernd@bsbernd.com>
Subject: Re: [PATCH 5.15] fuse: Fix race condition in writethrough path A race
Date: Tue, 14 Oct 2025 12:21:48 -0400 [thread overview]
Message-ID: <aO54nHhk_R1rs6X8@bfoster> (raw)
In-Reply-To: <CAJfpegvkJQ2eW4dpkKApyGSwuXDw8s3+Z1iPH+uBO-AuGpfReQ@mail.gmail.com>
On Tue, Oct 14, 2025 at 06:10:45PM +0200, Miklos Szeredi wrote:
> On Tue, 14 Oct 2025 at 15:57, Brian Foster <bfoster@redhat.com> wrote:
>
> > But TBH, if the writeback thing or something similarly simple works for
> > resolving the immediate bug, I wouldnt worry too much about it
> > until/unless there are userspace fs' explicitly looking for that sort of
> > behavior. Just my .02.
>
> Agreed.
>
> I just feel it unfortunate that this is default in libfuse and so many
> filesystems will have auto_inval_data enabled which don't even need
> it, and some mixed read-write workloads suffering badly as a
> consequence.
>
Maybe it didnt really need to be on by default? I don't recall caring
much about that (but again, long time ago) as long as the fs that wants
it can enable it.
Brian
> Thanks,
> Miklos
>
next prev parent reply other threads:[~2025-10-14 16:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 11:06 [PATCH 5.15] fuse: Fix race condition in writethrough path A race guangming.zhao
2025-10-09 22:11 ` Joanne Koong
[not found] ` <CAFS-8+VcZn7WZgjV9pHz4c8DYHRdP0on6-er5fm9TZF9RAO0xQ@mail.gmail.com>
2025-10-10 6:25 ` lu gu
2025-10-10 8:46 ` Miklos Szeredi
2025-10-13 13:39 ` Miklos Szeredi
2025-10-13 17:44 ` Brian Foster
2025-10-13 18:23 ` Miklos Szeredi
2025-10-13 18:53 ` Brian Foster
2025-10-14 7:48 ` Miklos Szeredi
2025-10-14 12:43 ` Miklos Szeredi
2025-10-14 16:15 ` Miklos Szeredi
2025-10-14 17:01 ` Joanne Koong
2025-10-14 17:56 ` Brian Foster
2025-10-15 3:59 ` lu gu
2025-10-15 14:09 ` Miklos Szeredi
2025-10-15 17:19 ` Joanne Koong
2025-10-15 19:48 ` Brian Foster
2025-10-15 20:28 ` Joanne Koong
2025-10-20 10:10 ` lu gu
2025-10-14 14:01 ` Brian Foster
2025-10-14 16:10 ` Miklos Szeredi
2025-10-14 16:15 ` Bernd Schubert
2025-10-14 16:21 ` Brian Foster [this message]
2025-10-13 20:16 ` Bernd Schubert
2025-10-13 20:27 ` Joanne Koong
2025-10-13 20:40 ` Bernd Schubert
2025-10-13 23:32 ` Joanne Koong
2025-10-14 8:06 ` Miklos Szeredi
2025-10-13 23:43 ` Joanne Koong
2025-10-14 8:11 ` Miklos Szeredi
2025-10-14 9:36 ` lu gu
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=aO54nHhk_R1rs6X8@bfoster \
--to=bfoster@redhat.com \
--cc=bernd@bsbernd.com \
--cc=giveme.gulu@gmail.com \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.