odd code in xfs

xfs

odd code in xfs_remove

To:	xfs@xxxxxxxxxxx
Subject:	odd code in xfs_remove
From:	Christoph Hellwig <hch@xxxxxx>
Date:	Thu, 10 Apr 2008 20:54:45 +0200
Sender:	xfs-bounce@xxxxxxxxxxx
User-agent:	Mutt/1.3.28i

unlike xfs_rmdir or xfs_rename xfs_remove always passes 0 instead of the
reserved blocks to xfs_dir_removename which means the latter always
operated in the ENOSPC mode.  This seems rather strange to me, so a
second pair of eyes, especially on a tree with history back to day 0
would be nice.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
odd code in xfs_remove, Christoph Hellwig <= Re: odd code in xfs_remove, David Chinner Re: odd code in xfs_remove, Christoph Hellwig

Previous by Date:	[PATCH 2/2] kill usesless IHOLD calls in xfs_remove and xfs_rmdir, Christoph Hellwig
Next by Date:	[PATCH 2/2] simplify xfs_lock_for_rename, Christoph Hellwig
Previous by Thread:	[PATCH 2/2] kill usesless IHOLD calls in xfs_remove and xfs_rmdir, Christoph Hellwig
Next by Thread:	Re: odd code in xfs_remove, David Chinner
Indexes:	[Date] [Thread] [Top] [All Lists]