From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Herrmann Subject: Re: [PATCH 0/6] File Sealing & memfd_create() Date: Fri, 11 Apr 2014 00:57:17 +0200 Message-ID: References: <1395256011-2423-1-git-send-email-dh.herrmann@gmail.com> <20140320153250.GC20618@thunk.org> <20140320163806.GA10440@thunk.org> <5346ED93.9040500@amacapital.net> <20140410203246.GB31614@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Theodore Ts'o , Ryan Lortie , Greg Kroah-Hartman , Kay Sievers , linux-kernel , "dri-devel@lists.freedesktop.org" , Daniel Mack , linux-mm , "Michael Kerrisk \(man-pages\)" , Lennart Poettering , linux-fsdevel , Andrew Morton , Linus Torvalds To: Andy Lutomirski Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" List-Id: linux-fsdevel.vger.kernel.org Hi On Thu, Apr 10, 2014 at 11:16 PM, Andy Lutomirski wrote: > Would it make sense for the initial mode on a memfd inode to be 000? > Anyone who finds this to be problematic could use fchmod to fix it. memfd_create() should be subject to umask() just like anything else. That should solve any possible race here, right? Thanks David