Re: [RFC][PATCH] ensure i_ino uniqueness in filesystems without permanent inode numbers (via idr)

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

 



On Tue, Nov 14, 2006 at 03:22:08PM -0500, Jeff Layton wrote:
> This patch is a first step at correcting these problems. It declares a
> new file_system_type flag (FS_I_INO_DYNAMIC). If this is set, then when
> new_inode is called, we'll use the IDR functions to generate a unique
> 31-bit value, leaving the first 100 inode numbers for statically
> allocated stuff like root inodes, etc. At inode deletion time, we
> idr_remove it so the i_ino value can be reused.

NAK.  All calls of new_inode() are triggered from within fs code;
there's no reason to introduce flags (which should be the last
resort) when you bloody well can have a separate helpers for that
case and have them called.  Explicitly.
-
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