From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 2/2] add f_flags to struct statfs(64) Date: Sat, 26 Jun 2010 15:09:28 +0200 Message-ID: <20100626130928.GA1838@lst.de> References: <20100626093507.GB26371@lst.de> <20100626095652.GI29809@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , viro@zeniv.linux.org.uk, drepper@redhat.com, linux-fsdevel@vger.kernel.org To: Nick Piggin Return-path: Received: from verein.lst.de ([213.95.11.210]:38679 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755229Ab0FZNJq (ORCPT ); Sat, 26 Jun 2010 09:09:46 -0400 Content-Disposition: inline In-Reply-To: <20100626095652.GI29809@laptop> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, Jun 26, 2010 at 07:56:53PM +1000, Nick Piggin wrote: > Is f_favail important enough to add as well? As Uli if he needs it. Adding real support for it won't be quite as easy as adding f_flags, as the individual filesystems would need to support it. And those not derived from FFS generally don't have any different accounting of inodes allocates vs inodes allocated to non-root user. In fact faking up any kind of free inodes values is already difficult enough for modern filesystems.