mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: livewire@gentoo.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.62 oops
Date: Mon, 17 Feb 2003 19:42:30 -0800	[thread overview]
Message-ID: <20030217194230.7bf6f97b.akpm@digeo.com> (raw)
In-Reply-To: <200302172229.21528.livewire@gentoo.org>

Bob Johnson <livewire@gentoo.org> wrote:
>
> Running a stress test of 50 concurrent kernel tree cp's + md5sum the files on
> 2.5.62 results in the following:
> 
> Feb 17 21:53:41 livewire kernel: VFS: brelse: Trying to free free buffer
> Feb 17 21:53:41 livewire kernel: buffer layer error at fs/buffer.c:1170
> Feb 17 21:53:41 livewire kernel: Pass this trace through ksymoops for 
> reporting

It's not really an oops, although the bug which this is reporting could cause
a crash.

It is a known problem in the htree indexed directory code.  I can reproduce
it, but haven't had time to work on it.  Chris Li has time to work on it,
but cannot reproduce it.

We'll get there.


      reply	other threads:[~2003-02-18  3:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18  3:29 Bob Johnson
2003-02-18  3:42 ` 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=20030217194230.7bf6f97b.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=livewire@gentoo.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

all inboxes | Powered by JetHome®