From: Christoph Hellwig <hch@infradead.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Christoph Hellwig <hch@infradead.org>,
Pavel Emelyanov <xemul@scylladb.com>,
linux-fsdevel@vger.kernel.org,
"Raphael S . Carvalho" <raphaelsc@scylladb.com>,
linux-api@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] fs: Propagate FMODE_NOCMTIME flag to user-facing O_NOCMTIME
Date: Mon, 6 Oct 2025 22:08:45 -0700 [thread overview]
Message-ID: <aOSgXXzvuq5YDj7q@infradead.org> (raw)
In-Reply-To: <CALCETrVsD6Z42gO7S-oAbweN5OwV1OLqxztBkB58goSzccSZKw@mail.gmail.com>
On Sat, Oct 04, 2025 at 09:08:05AM -0700, Andy Lutomirski wrote:
> > Well, we'll need to look into that, including maybe non-blockin
> > timestamp updates.
> >
>
> It's been 12 years (!), but maybe it's time to reconsider this:
>
> https://lore.kernel.org/all/cover.1377193658.git.luto@amacapital.net/
I don't see how that is relevant here. Also writes through shared
mmaps are problematic for so many reasons that I'm not sure we want
to encourage people to use that more.
next prev parent reply other threads:[~2025-10-07 5:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251003093213.52624-1-xemul@scylladb.com>
2025-10-04 4:26 ` [PATCH] fs: Propagate FMODE_NOCMTIME flag to user-facing O_NOCMTIME Christoph Hellwig
2025-10-04 16:08 ` Andy Lutomirski
2025-10-07 5:08 ` Christoph Hellwig [this message]
2025-10-08 15:22 ` Andy Lutomirski
2025-10-08 21:27 ` Dave Chinner
2025-10-08 21:51 ` Andy Lutomirski
2025-10-11 1:35 ` Dave Chinner
2025-10-11 4:04 ` Andy Lutomirski
2025-10-10 5:27 ` Christoph Hellwig
2025-10-10 17:35 ` Andy Lutomirski
2025-10-05 22:06 ` Dave Chinner
2025-10-07 5:10 ` Christoph Hellwig
2025-10-05 23:38 ` Dave Chinner
2025-10-06 2:16 ` Theodore Ts'o
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=aOSgXXzvuq5YDj7q@infradead.org \
--to=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=raphaelsc@scylladb.com \
--cc=xemul@scylladb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).