linux-kernel - Re: [PATCH 4/4] eCryptfs: ino

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060825221615.GA11613@us.ibm.com>
Date:	Fri, 25 Aug 2006 17:16:15 -0500
From:	Michael Halcrow <mhalcrow@...ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] eCryptfs: ino_t to u64 for filldir

On Fri, Aug 25, 2006 at 10:51:17PM +0100, David Howells wrote:
> Michael Halcrow <mhalcrow@...ibm.com> wrote:
> > filldir()'s inode number is now type u64 instead of ino_t.
> 
> Btw, in ecryptfs_interpose(), you have:
> 
> 	inode = iget(sb, lower_inode->i_ino);
> 
> But you have to be *very* *very* careful doing that.  i_ino may be
> ambiguous.  My suggestions to make i_ino bigger were turned down by
> Al Viro; and even it were bigger, it might still not be unique.

Is this the case as long as we stay under the same mountpoint?

Mike
-
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/