why fs/*/*.c don't use i_size_read/write?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I see a lot of file system code in fs/*/*.c which does not use i_size_read
and i_size_write (some of it does but not all).  Does that mean that all of
those file systems (including ext3 and such) are not safe under certain
conditions?! (e.g., 32-bit SMP/PREMPT kernels as per the comment above
i_size_read in fs.h)

Should everyone use i_size_read/write exclusively?

If not, are there conditions where it's safe not to use these helpers and
you can access inode->i_size directly?  I couldn't find documentation to
suggest that dereferencing inode->i_size is ok at times.

Thanks,
Erez.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux