linux-kernel - Re: Crash in 2.6.28.7

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

Message-ID: <20090226160829.GH7227@mit.edu>
Date:	Thu, 26 Feb 2009 11:08:29 -0500
From:	Theodore Tso <tytso@....edu>
To:	Fabio Comolli <fabio.comolli@...il.com>
Cc:	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Crash in 2.6.28.7 - ext4 related

I got the crash image.  Unfortunately the beginning of the Oops
message was cut off, which might have been valuable.  There are some
new patches that are newer than what has been backported to 2.6.28.7;
some of them are in the for-stable branch of the ext4 git tree, and
have been queued for 2.6.28.8.  The call stack doesn't look like one
of the known bugs, though.

Hmm... can you send us the output of dumpe2fs on the filesystem?  And
something that would be very useful would be a raw e2image of the
filesystem, created thusly:

	    e2image -r /dev/sdXXX - | bzip2 > sdXXX.e2i.bz2

This image will contain the basic filesystem metadata, including the
directory blocks (and directory names), but none of the data blocks.
It is therefore much smaller, and if you are willing to let me see
your directory file names, I can take that image and try to replicate
the problem on one of my systems.

If you have a spare 20gb of disk space, you can also unpack the raw
image dump and try reproducing the problem on the raw image dump.  If
you can trigger it easily with an rm -rf operation, it should be just
as reproducible on the raw image dump.

Regards,

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