| 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
| ||
|
Message-ID: <AANLkTilbFzwOib6sF-uz8v2c_1LA2UgnnoPWZ4DtDUJK@mail.gmail.com> Date: Mon, 12 Jul 2010 18:37:03 -0700 From: "Patrick J. LoPresti" <lopresti@...il.com> To: Dave Chinner <david@...morbit.com> Cc: Andreas Dilger <adilger@...ger.ca>, ocfs2-devel@....oracle.com, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org Subject: Re: [PATCH 2/2] OCFS2: Allow huge (> 16 TiB) volumes to mount On Mon, Jul 12, 2010 at 6:25 PM, Dave Chinner <david@...morbit.com> wrote: > > The XFS code is different to the above because there is still a 16TB > size limit on 32 bit systemsi (i.e. page cache address limits). IOWs, > you can't just remove the above 16TB check unless you (i.e. OCFS2) > handle >16TB block devices on 32 bit systems correctly... If you look at my patch, you will see that is precisely what it does. As the comments indicate, it uses the exact same check as ext4, which will correctly refuse to mount huge volumes on 32-bit systems. The XFS test appears to be the same thing written a little differently. Andreas is suggesting that somebody should factor out this check into a common library routine. That sounds like a fine idea, but it also sounds orthogonal to the (simple and useful) patch I am attempting to submit. - Pat -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists