From: Christoph Hellwig <hch@infradead.org>
To: viro@zeniv.linux.org.uk, torvalds@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: why is O_TMPFILE multiplexed over open() instead of being a separate syscall?
Date: Thu, 1 Aug 2013 01:42:53 -0700 [thread overview]
Message-ID: <20130801084253.GA4727@infradead.org> (raw)
Sorry for being a bit late to the game, but..
Why is the useful tmpfile functionality multiplexed over open when it
has very different semantics from a normal open?
In addition to the flag problems already discussed to death it also just
leads to splattering of the code in the implementaiton, given that
path_openat branches out really early in path_openat.
What's the problem with a clear single purpose tmpfile() system call?
next reply other threads:[~2013-08-01 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 8:42 Christoph Hellwig [this message]
2013-08-02 12:59 ` why is O_TMPFILE multiplexed over open() instead of being a separate syscall? Jeff Layton
2013-08-08 11:47 ` Michael Kerrisk
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=20130801084253.GA4727@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).