From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: A few ext4dev images for which fsck segfaults on the next branch...
Date: Tue, 18 Mar 2008 13:50:22 -0500 [thread overview]
Message-ID: <47E00EEE.3070305@redhat.com> (raw)
Just in case anyone is bored... :)
http://sandeen.fedorapeople.org/ext4/fsck-segfault-images/
contains about 6 intentionally-corrupted ext4dev images which each cause
the e2fsck in the next branch to segfault for me on x86_64.
I'll find some time to look closer, but just thought I'd put them out
there for now.
-Eric
reply other threads:[~2008-03-19 21:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E00EEE.3070305@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.