linux-ext4 - tune2fs -I seems dangerous

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 for Android: free password hash cracker in your pocket

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

Message-ID: <49385927.9070003@redhat.com>
Date:	Thu, 04 Dec 2008 16:26:47 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	ext4 development <linux-ext4@...r.kernel.org>
Subject: tune2fs -I seems dangerous

As a small experiment...

dd if=/dev/zero of=fsfile bs=1M count=16
mkfs.ext4 -F -I 128 fsfile
mkdir -p mnt
mount -o loop fsfile mnt
for I in `seq 1 4096`; do echo $I > mnt/file.$I; done
umount mnt
tune2fs -I 256 fsfile
e2fsck -fy fsfile

... this yields 10031 lines of fsck output, and results in about 38% of
the files that were on the filesystem going missing.

I don't have the strong sense that tune2fs -I has been shaken out at
all; should it be shipping as a useable option?

Thanks,
-Eric




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