From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zeniv.linux.org.uk ([195.92.253.2]:33438 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S968980AbdD0VKI (ORCPT ); Thu, 27 Apr 2017 17:10:08 -0400 Date: Thu, 27 Apr 2017 22:10:05 +0100 From: Al Viro To: Linus Torvalds Cc: Christoph Hellwig , linux-fsdevel Subject: Re: completely ignore unknown open flags Message-ID: <20170427211005.GF29622@ZenIV.linux.org.uk> References: <20170427074225.13230-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Apr 27, 2017 at 12:41:39PM -0700, Linus Torvalds wrote: > On Thu, Apr 27, 2017 at 12:42 AM, Christoph Hellwig wrote: > > This is the fallout from the reject unknown flags discussion a few > > weeks back. So to keep backwards compatibily we can't _reject_ unknown > > flags. But we'd better totally ignore them and don't pass them to > > file systems or back to userspace using fcntl. > > Ack, this makes sense to me. It's crazy to let fcntl etc show bits > that the kernel isn't even using. > > I'm assuming this will come through Al eventually. It doesn't seem > high-priority for me to worry about it just before the 4.11 release, > but it might be worth marking for stable just to percolate the change > eventually to other kernels, and keep these kinds of differences > minimal. Applied tonight, still hadn't pushed it out into -next - the tree goes through testing.