linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lutomirski <andy@luto.us>
To: Theodore Tso <tytso@mit.edu>, Andrew Lutomirski <andy@luto.us>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: 2.6.32-rc1 oops in ext4
Date: Thu, 1 Oct 2009 12:42:45 -0400	[thread overview]
Message-ID: <cb0375e10910010942m31c40ff5kc261deaa87969e55@mail.gmail.com> (raw)
In-Reply-To: <20091001030733.GS24383@mit.edu>

On Wed, Sep 30, 2009 at 11:07 PM, Theodore Tso <tytso@mit.edu> wrote:
> On Wed, Sep 30, 2009 at 10:54:26PM -0400, Andrew Lutomirski wrote:
>> All I did was boot Fedora 11 and open a Konsole.  I'm running
>> 84d88d5d4efc37dfb8a93a4a58d8a227ee86ffa4.
>
> I'm pretty sure this patch should fix things; can you confirm?
>
>                                              - Ted
>
> commit 1f94533d9cd75f6d2826018d54a971b9cc085992
> Author: Theodore Ts'o <tytso@mit.edu>
> Date:   Wed Sep 30 22:57:41 2009 -0400
>
>    ext4: fix a BUG_ON crash by checking that page has buffers attached to it
>
>    In ext4_num_dirty_pages() we were calling page_buffers() before
>    checking to see if the page actually had pages attached to it; this
>    would cause a BUG check crash in the inline function page_buffers().
>
>    Thanks to Markus Trippelsdorf for reporting this bug.
>
>    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

I patched that onto the same kernel from git and it seems to work.

Tested-by: Andy Lutomirski <luto@mit.edu>

Thanks,
Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-10-01 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  2:54 2.6.32-rc1 oops in ext4 Andrew Lutomirski
2009-10-01  3:07 ` Theodore Tso
2009-10-01 16:42   ` Andrew Lutomirski [this message]

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=cb0375e10910010942m31c40ff5kc261deaa87969e55@mail.gmail.com \
    --to=andy@luto.us \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).