linux-kernel - i_ino 4 billion file limitation

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>] [day] [month] [year] [list]

Message-ID: <45B41F79.20409@wolfmountaingroup.com>
Date:	Sun, 21 Jan 2007 19:20:41 -0700
From:	"Jeffrey V. Merkey" <jmerkey@...fmountaingroup.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: i_ino 4 billion file limitation

I am now pushing up against the i_ino (unsigned long) file limitation 
when I use virtual inode numbers in DSFS.  This field needs to be increased
to 64 bit to allow more than 4 billion unique inode numbers.   I am 
running out of inode address space with the current architecture.

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/