linux-kernel - Re: ext3: fix ext3_dx_readdir hash collision handling

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]

Date:	Fri, 24 Oct 2008 06:41:52 -0400
From:	Theodore Tso <tytso@....edu>
To:	Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc:	linux-kernel@...r.kernel.org, eugene@...ix.com, msnitzer@...ix.com,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org
Subject: Re: ext3: fix ext3_dx_readdir hash collision handling - Regression

On Fri, Oct 24, 2008 at 06:28:51AM +0200, Markus Trippelsdorf wrote:
> 
> Notice that I don't use "rm -rf" but "rm -r". The problem only occurs
> when I run "rm -r" without the "-f" switch.
> 

Still having trouble reproducing it.  I'll try to look more at your
.config.  One difference i can see right off the bat is that I'm still
using an 32-bit x86 system, not a 64-bit x86 system.  That shouldn't
make a difference, though....

							- Ted

Script started on Fri 24 Oct 2008 06:36:47 AM EDT
Top-level shell (parent script)
Using forwarded ssh authentication socket
<tytso.root@...sure> {/usr/projects/linux/ext4}  [btree-debug]
498# mke2fs -t ext3 /dev/thunk/testext4
mke2fs 1.41.3 (12-Oct-2008)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
<tytso.root@...sure> {/usr/projects/linux/ext4}  [btree-debug]
499# debugfs -w /dev/thunk/testext4
debugfs 1.41.3 (12-Oct-2008)
debugfs:  ssv s_hash_seed c3188d40-b161-4458-b3f9-22ca7788110f
debugfs:  ssv s_def_hash_version tea
debugfs:  q
<tytso.root@...sure> {/usr/projects/linux/ext4}  [btree-debug]
500# mount /dev/thunk/testext4 /mnt
<tytso.root@...sure> {/usr/projects/linux/ext4}  [btree-debug]
501# tar -C /mnt -xjf /usr/projects/lin.ux/linux-2.6.27.2.tar.bz2 
<tytso.root@...sure> {/usr/projects/linux/ext4}  [btree-debug]
502# /bin/rm -r /mnt/linux-2.6.27.2/
<tytso.root@...sure> {/usr/projects/linux/ext4}  [btree-debug]
503# umount /mnt/
<tytso.root@...sure> {/usr/projects/linux/ext4}  [btree-debug]
504# uname -a
Linux closure 2.6.27-00067-g5593f6c-dirty #13 SMP Thu Oct 23 22:22:03 EDT 2008 i686 GNU/Linux
<tytso.root@...sure> {/usr/projects/linux/ext4}  [btree-debug]
505# exit

Script done on Fri 24 Oct 2008 06:39:22 AM EDT
--
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/