mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.5.56
Date: Sat, 11 Jan 2003 06:47:27 +0100	[thread overview]
Message-ID: <20030111064727.0e494512.us15@os.inf.tu-dresden.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301101222510.1856-100000@penguin.transmeta.com>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

On Fri, 10 Jan 2003 12:26:56 -0800 (PST) Linus Torvalds (LT) wrote:

LT> Summary of changes from v2.5.55 to v2.5.56
LT> ============================================

Hello,

I just got the following bug with 2.5.56 pretty much out of the blue:

VFS: brelse: Trying to free free buffer
buffer layer error at fs/buffer.c:1182
Call Trace:
 [<c0147105>] __brelse+0x35/0x40
 [<c01472c9>] bh_lru_install+0xa9/0xe0
 [<c0147371>] __find_get_block+0x71/0x80
 [<c0146fa3>] __getblk_slow+0x23/0x100
 [<c01473cf>] __getblk+0x4f/0x60
 [<c01473ff>] __bread+0x1f/0x40
 [<c0180265>] ext3_get_inode_loc+0xe5/0x190
 [<c018033f>] ext3_read_inode+0x2f/0x390
 [<c015cd5e>] iget_locked+0x6e/0x70
 [<c0182908>] ext3_lookup+0xe8/0x100
 [<c0151330>] real_lookup+0xc0/0x100
 [<c015159a>] do_lookup+0x11a/0x170
 [<c01519e2>] link_path_walk+0x3f2/0x790
 [<c0152239>] __user_walk+0x49/0x60
 [<c014d8fc>] vfs_lstat+0x1c/0x60
 [<c014df3b>] sys_lstat64+0x1b/0x40
 [<c010933b>] syscall_call+0x7/0xb

Regards,
-Udo.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-01-11  5:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 20:26 Linus Torvalds
2003-01-11  5:47 ` Udo A. Steinberg [this message]
2003-01-11  6:20   ` Andrew Morton
2003-01-11  9:43 ` Adrian Bunk
2003-01-11  9:56   ` Zwane Mwaikambo
2003-01-11 23:57   ` Dave Jones
2003-01-12  0:02 ` Dave Jones

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=20030111064727.0e494512.us15@os.inf.tu-dresden.de \
    --to=us15@os.inf.tu-dresden.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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®