From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f65.google.com ([74.125.83.65]:32847 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753214AbdCTRMP (ORCPT ); Mon, 20 Mar 2017 13:12:15 -0400 Date: Mon, 20 Mar 2017 10:11:42 -0700 From: Eric Biggers To: linux-fsdevel@vger.kernel.org Cc: Alexander Viro , David Howells , mtk.manpages@gmail.com, Christoph Hellwig , "Darrick J . Wong" , Linux API , linux-xfs@vger.kernel.org, Eric Biggers Subject: Re: [PATCH] statx: reject unknown flags when using NULL path Message-ID: <20170320171142.GA26906@gmail.com> References: <20170311065823.4415-1-ebiggers3@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170311065823.4415-1-ebiggers3@gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Mar 10, 2017 at 10:58:23PM -0800, Eric Biggers wrote: > From: Eric Biggers > > The statx() system call currently accepts unknown flags when called with > a NULL path to operate on a file descriptor. Left unchanged, this could > make it hard to introduce new query flags in the future, since > applications may not be able to tell whether a given flag is supported. > > Fix this by failing the system call with EINVAL if any flags other than > KSTAT_QUERY_FLAGS are specified in combination with a NULL path. > Does anyone have comments on this patch? I really think we need to get this in before v4.11 is released, since it deals with the API. - Eric