On 2012-04-26, at 6:51 PM, Dave Chinner wrote:
On Thu, Apr 26, 2012 at 02:32:36PM +0100, David Howells wrote:
I wonder if there's a way to make this explicit - or is it something that if the bit isn't set, you can't use the value in st_blksize. I wonder if this value always has to be non-zero to make sure existing stat() doesn't explode.
More likely it probably needs to be non-zero to prevent applications doing division by block size from exploding... ;)
Right, and any application which knows it needs the blocksize should also be requesting it when using the statxat() (or whatever) syscall.
Cheers, Andreas