Re: [RFC 2/7] cramfs: create unique inode numbers

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

 



On Sun, 1 June 2008 23:24:51 +0200, Arnd Bergmann wrote:
> On Sunday 01 June 2008, Jörn Engel wrote:
> > 
> > Couldn't this cause problems for NFS?  The same inode no longer has a
> > stable inode number across reboots.  Basing on dentry location can also
> > be an information leak and cause problems on 64bit machines with old
> > userspace.
> 
> Sorry if I was not clear with this: I meant dentry location on disk,
> not in memory. So the inode number is still stable across reboots and
> does not leak data, it is just different from before.

In that case I'd better retract my whole comment. ;)

Jörn

-- 
All art is but imitation of nature.
-- Lucius Annaeus Seneca
--
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