lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 2 Jun 2008 07:42:49 +0200 From: Jörn Engel <joern@...fs.org> To: Arnd Bergmann <arnd@...db.de> Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, hch@....de Subject: Re: [RFC 2/7] cramfs: create unique inode numbers 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-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists