From: Al Viro <viro@zeniv.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Chirantan Ekbote <chirantan@chromium.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Dylan Reid <dgreid@chromium.org>,
Suleiman Souhlal <suleiman@chromium.org>,
fuse-devel <fuse-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2/2] fuse: Implement O_TMPFILE support
Date: Fri, 13 Nov 2020 12:28:45 +0000 [thread overview]
Message-ID: <20201113122845.GG3576660@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAJfpegv4X2m=-N69iB+Q_6fneeX_0uMNyzkVqfU+qQXdqXSUNw@mail.gmail.com>
On Fri, Nov 13, 2020 at 11:52:09AM +0100, Miklos Szeredi wrote:
> It's the wrong interface, and we'll have to live with it forever if we
> go this route.
>
> Better get the interface right and *then* think about the
> implementation. I don't think adding ->atomic_tmpfile() would be that
> of a big deal, and likely other distributed fs would start using it in
> the future.
Let me think about it; I'm very unhappy with the amount of surgery it has
taken to somewhat sanitize the results of ->atomic_open() introduction, so
I'd prefer to do it reasonably clean or not at all.
next prev parent reply other threads:[~2020-11-13 12:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 10:03 [PATCH 0/2] Support for O_TMPFILE in fuse Chirantan Ekbote
2020-11-09 10:03 ` [PATCH 1/2] uapi/fuse.h: Add message definitions for O_TMPFILE Chirantan Ekbote
2020-11-09 10:03 ` [PATCH 2/2] fuse: Implement O_TMPFILE support Chirantan Ekbote
2020-11-09 11:37 ` Miklos Szeredi
2020-11-10 3:33 ` Chirantan Ekbote
2020-11-10 7:52 ` Miklos Szeredi
2020-11-13 5:19 ` Chirantan Ekbote
2020-11-13 10:52 ` Miklos Szeredi
2020-11-13 12:28 ` Al Viro [this message]
2020-11-13 13:54 ` Miklos Szeredi
2022-08-31 2:57 ` Yu-Li Lin
2022-08-31 12:19 ` Miklos Szeredi
2022-08-31 21:30 ` Yu-li Lin
2022-09-05 15:51 ` Miklos Szeredi
2022-09-06 4:58 ` Amir Goldstein
2022-09-06 5:29 ` Al Viro
2022-09-06 7:23 ` Miklos Szeredi
2022-09-13 1:51 ` Al Viro
2022-09-13 10:20 ` Miklos Szeredi
2022-09-18 13:17 ` [fuse-devel] " Stef Bon
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=20201113122845.GG3576660@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=chirantan@chromium.org \
--cc=dgreid@chromium.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=suleiman@chromium.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;
as well as URLs for NNTP newsgroup(s).