From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eric Rannaud <e@nanocritical.com>,
Andy Lutomirski <luto@amacapital.net>,
Christoph Hellwig <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC PATCH] fs: allow open(dir, O_TMPFILE|..., 0) with mode 0
Date: Wed, 5 Nov 2014 00:27:21 -0800 [thread overview]
Message-ID: <20141105082721.GB19607@infradead.org> (raw)
In-Reply-To: <CA+55aFw29MUj+w46yneut2yxXOH1RQmDud5KL8V-SPyPWm1WqA@mail.gmail.com>
On Mon, Nov 03, 2014 at 11:04:27AM -0800, Linus Torvalds wrote:
> Oh, so you don't actually need any file contents at all?
>
> If that is actually a real usage, then maybe we should just say that
> "O_TMPFILE|O_RDONLY" is fine, and remove the check that it has to be
> writable.
Wasn't this disallowed to prevent problems on old kernels that don't use
O_TMPFILE? In that case we'd ignore the flag and would just get a file
handle for the directory instead.
next prev parent reply other threads:[~2014-11-05 8:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 9:08 [RFC PATCH] fs: allow open(dir, O_TMPFILE|..., 0) with mode 0 Eric Rannaud
2014-10-30 21:48 ` Andy Lutomirski
2014-10-30 22:48 ` Linus Torvalds
2014-10-30 22:58 ` Linus Torvalds
2014-10-31 0:01 ` Andy Lutomirski
2014-10-31 0:59 ` Linus Torvalds
2014-10-31 8:42 ` Christoph Hellwig
2014-10-31 18:44 ` Andy Lutomirski
2014-10-31 18:53 ` Linus Torvalds
2014-11-03 8:34 ` Christoph Hellwig
2014-11-03 17:05 ` Linus Torvalds
2014-11-03 17:06 ` Andy Lutomirski
2014-11-03 18:49 ` Eric Rannaud
2014-11-03 19:04 ` Linus Torvalds
2014-11-05 8:27 ` Christoph Hellwig [this message]
2014-11-05 15:21 ` Eric Rannaud
2014-11-05 15:32 ` Andy Lutomirski
2014-11-05 17:10 ` Linus Torvalds
2014-11-03 22:07 ` Jeremy Allison
2014-11-05 8:25 ` Christoph Hellwig
2014-10-31 0:57 ` Eric Rannaud
2014-10-31 1:04 ` Linus Torvalds
2014-10-31 2:12 ` Eric Rannaud
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=20141105082721.GB19607@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=e@nanocritical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).