From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id p8TB5W1f185288 for ; Thu, 29 Sep 2011 06:05:32 -0500 Date: Thu, 29 Sep 2011 07:05:28 -0400 From: Christoph Hellwig Subject: Re: [PATCH] xfsprogs: xfs_quota: don't print invalid quota file inode number Message-ID: <20110929110528.GA509@infradead.org> References: <43b1c14570decac4b102616fb8e9b14d101edc39.1317208532.git.aelder@sgi.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <43b1c14570decac4b102616fb8e9b14d101edc39.1317208532.git.aelder@sgi.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Alex Elder Cc: xfs@oss.sgi.com On Wed, Sep 28, 2011 at 06:15:37AM -0500, Alex Elder wrote: > When the state of quota files is dumped, xfs_quota blindly shows > whatever inode number is returned by the kernel. If one of the > quota types is not enabled or enforced, the inode number provided > is an invalid value ((__u64) -1). Rather than print a meaningless > large integer, print "N/A" in its place to make interpreting the > result it a little more obvious. > > Signed-off-by: Alex Elder Looks good, Reviewed-by: Christoph Hellwig _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs