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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 8 Feb 2021 23:23:29 -0500 From: "Theodore Ts'o" <tytso@....edu> To: Andreas Dilger <adilger@...mcloud.com> Cc: linux-ext4@...r.kernel.org Subject: Re: [PATCH] e2fsck: fix check of directories over 4GB On Tue, Feb 02, 2021 at 01:25:49AM -0700, Andreas Dilger wrote: > If directories grow larger than 4GB in size with the large_dir > feature, e2fsck will consider them to be corrupted and clear > the high bits of the size. > > Since it isn't very common to have directories this large, and > unlike sparse files that don't have ill effects if the size is > too large, an too-large directory will have all of the sparse > blocks filled in by e2fsck, so huge directories should still > be viewed with suspicion. Check for consistency between two of > the three among block count, inode size, and superblock large_dir > flag before deciding whether the directory inode should be fixed > or cleared, or if large_dir should be set in the superblock. > > Update the f_recnect_bad test case to match new output. > > Fixes: 49f28a06b738 ("e2fsck: allow to check >2GB sized directory") > Signed-off-by: Andreas Dilger <adilger@...mcloud.com> > Lustre-bug-id: https://jira.whamcloud.com/browse/LU-14345 > Change-Id: I1b898cdab95d239ba1a7b37eb96255acadce7057 Thanks, applied. - Ted
Powered by blists - more mailing lists