Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753677Ab3HERhV (ORCPT ); Mon, 5 Aug 2013 13:37:21 -0400 Received: from longford.logfs.org ([213.229.74.203]:59985 "EHLO longford.logfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753284Ab3HERhU (ORCPT ); Mon, 5 Aug 2013 13:37:20 -0400 Date: Mon, 5 Aug 2013 12:04:18 -0400 From: =?utf-8?B?SsO2cm4=?= Engel To: Christoph Hellwig Cc: Linus Torvalds , Andy Lutomirski , Al Viro , Linux Kernel Mailing List Subject: Re: O_TMPFILE fs corruption (Re: Linux 3.11-rc4) Message-ID: <20130805160418.GA470@logfs.org> References: <51FF0F18.5020705@mit.edu> <20130805082646.GA14689@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20130805082646.GA14689@infradead.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1078 Lines: 27 On Mon, 5 August 2013 01:26:46 -0700, Christoph Hellwig wrote: > On Sun, Aug 04, 2013 at 08:45:16PM -0700, Linus Torvalds wrote: > > The patch looks right to me - we should pass in similar flags for the > > create case as for tmpfile to the filesystem. > > > > But let's make sure we're all on the same page. Al? > > Given all the problems and very limited fs support I'd much prefer > disabling O_TMPFILE for this release. That'd give it the needed > exposure it was missing by being merged without any previous public > review. Agreed. This has not been in -next at all. It is not an urgent security thing or regression fix, so there is no good excuse for avoiding the normal process. Jörn -- For a successful technology, reality must take precedence over public relations, for nature cannot be fooled. -- Richard Feynman -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/