From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC PATCH] fs: allow open(dir, O_TMPFILE|..., 0) with mode 0 Date: Fri, 31 Oct 2014 01:42:20 -0700 Message-ID: <20141031084220.GA29085@infradead.org> References: <4e8f7a1abcf5e0527ef8968143b2d0fcae48f5f4.1414658968.git.e@nanocritical.com> <5452B241.5010603@amacapital.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , Eric Rannaud , Linux Kernel Mailing List , Alexander Viro , linux-fsdevel , Andrew Morton To: Andy Lutomirski Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Oct 30, 2014 at 05:01:30PM -0700, Andy Lutomirski wrote: > > flink()), the mode really matters. So this idiotic glibc behavior of > > only forwarding the third argument if O_CREAT is set seems to be a > > bug. > > We could bite the bullet and add a tmpfile syscall. /me ducks I've got another use case for that: Samba. It wants to inherit all kinds of attributes (xattrs, modes, etc) during file creation, and right now it's doing it in a racy way. I've come up with a patch to use O_TEMPFILE + flink, but it turns out that Samba may as well be asked to create read-only files, which we can't create using O_TMPFILE.