From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14472] EXT4 corruption
Date: Thu, 29 Oct 2009 21:31:10 GMT [thread overview]
Message-ID: <200910292131.n9TLVARY005771@demeter.kernel.org> (raw)
In-Reply-To: <bug-14472-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14472
--- Comment #1 from Rafael J. Wysocki <rjw@sisk.pl> 2009-10-29 21:31:10 ---
On Thursday 29 October 2009, Andrew Lutomirski wrote:
> On Mon, Oct 26, 2009 at 2:55 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.31. Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14472
> > Subject : EXT4 corruption
> > Submitter : Shawn Starr <shawn.starr@rogers.com>
> > Date : 2009-10-13 2:07 (14 days old)
> > References : http://marc.info/?l=linux-kernel&m=125539997508256&w=4
> > Handled-By : Theodore Tso <tytso@mit.edu>
> >
>
>
> This but is *not* fixed. I just triggered it a few minutes ago by
> abusing i915 and drm, which caused a panic. This is slightly newer
> than 2.6.32-rc5, with a couple of i915 bugfixes thrown in.
>
> Photos are here:
> http://web.mit.edu/luto/www/ext4_crashphotos/
>
> This is a very nasty regression, for obvious reasons.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-10-29 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 16:52 [Bug 14472] New: EXT4 corruption bugzilla-daemon
2009-10-29 21:31 ` bugzilla-daemon [this message]
2009-10-29 21:38 ` [Bug 14472] " bugzilla-daemon
2009-10-29 21:44 ` bugzilla-daemon
2009-11-17 22:30 ` bugzilla-daemon
2009-11-17 22:31 ` bugzilla-daemon
2009-11-17 22:31 ` bugzilla-daemon
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=200910292131.n9TLVARY005771@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).