public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Paolo Ciarrocchi <ciarrocchi@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops with 2.5.47-mm2
Date: Wed, 13 Nov 2002 14:54:40 -0800	[thread overview]
Message-ID: <3DD2D830.5914E698@digeo.com> (raw)
In-Reply-To: 20021113211539.21064.qmail@linuxmail.org

Paolo Ciarrocchi wrote:
> 
> Hi Andrew,
> I can reproduce an oops simply running fillmem 400
> 
> kernel is 2.5.47-mm2
> fs is ext3.
> 
> ..
> >>EIP; c012e137 <get_fs_type+7/30>   <=====

Sorry, don't know.  It doesn't happen here.  It looks like the
filesystem registration code was affected by the recent modules improvement.

If you can reproduce it, could you please test 2.5.47 plus 
just the -bk changes?  They are in
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.47/2.5.47-mm2/broken-out/linus.patch

      reply	other threads:[~2002-11-13 22:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 21:15 oops with 2.5.47-mm2 Paolo Ciarrocchi
2002-11-13 22:54 ` Andrew Morton [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=3DD2D830.5914E698@digeo.com \
    --to=akpm@digeo.com \
    --cc=ciarrocchi@linuxmail.org \
    --cc=linux-kernel@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