linux-kernel - Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)

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: <45829D94.1090304@redhat.com>
Date:	Fri, 15 Dec 2006 08:05:24 -0500
From:	Jeff Layton <jlayton@...hat.com>
To:	akpm@...l.org
CC:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent
 inode numbers (introduction)

Jeff Layton wrote:
 > Apologies for the long email, but I couldn't come up with a way to explain
 > this in fewer words. Many filesystems that are part of the linux kernel
 > have problems with how they have assign out i_ino values:
 >

If there are no further comments/suggestions on this patchset, I'd like to
ask Andrew to add it to -mm soon and target getting it rolled into 2.6.21.
Once it's in -mm, I'll start posting more patches to convert the other
filesystems.

Andrew, are the patches I've already posted sufficient, or should I resend
the set?

Thanks,
Jeff


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