LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: ext3-users@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: VFS: brelse: Trying to free free buffer
Date: Thu, 11 Dec 2003 09:19:23 +1100	[thread overview]
Message-ID: <87smjsgvtg.fsf@enki.rimspace.net> (raw)

I got this error in my log reports this morning, from the machine I use
as my firewall.  This is the first time it has occurred, but the machine
is running a very new kernel:

Linux fendrian.rimspace.net 2.6.0-test11-fendrian #1 Wed Dec 10 22:25:59 EST 2003 i486 GNU/Linux

The kernel was up to date as per the CVS repository at that point. This
was just before the CDROM_SEND_PACKET IOCTL fix went in.


There is a single ext3 partition on the machine, and it generally
doesn't do very much at all, especially not disk intensive stuff.

Please let me know if I can provide any more assistance in finding the
source of the problem, or resolving it.

Dec 11 04:03:55 fendrian kernel: VFS: brelse: Trying to free free buffer
Dec 11 04:03:55 fendrian kernel: buffer layer error at fs/buffer.c:1279
Dec 11 04:03:55 fendrian kernel: Call Trace:
Dec 11 04:03:56 fendrian kernel:  [__brelse+41/48] __brelse+0x29/0x30
Dec 11 04:03:56 fendrian kernel:  [bh_lru_install+124/176] bh_lru_install+0x7c/0xb0
Dec 11 04:03:56 fendrian kernel:  [__find_get_block+96/160] __find_get_block+0x60/0xa0
Dec 11 04:03:56 fendrian kernel:  [__getblk_slow+24/224] __getblk_slow+0x18/0xe0
Dec 11 04:03:56 fendrian kernel:  [__getblk+42/48] __getblk+0x2a/0x30
Dec 11 04:03:56 fendrian kernel:  [ext3_getblk+123/528] ext3_getblk+0x7b/0x210
Dec 11 04:03:56 fendrian kernel:  [submit_bio+61/112] submit_bio+0x3d/0x70
Dec 11 04:03:56 fendrian kernel:  [ll_rw_block+88/128] ll_rw_block+0x58/0x80
Dec 11 04:03:56 fendrian kernel:  [ext3_find_entry+288/976] ext3_find_entry+0x120/0x3d0
Dec 11 04:03:56 fendrian kernel:  [ext3_lookup+41/160] ext3_lookup+0x29/0xa0
Dec 11 04:03:56 fendrian kernel:  [__lookup_hash+108/160] __lookup_hash+0x6c/0xa0
Dec 11 04:03:56 fendrian kernel:  [open_namei+279/992] open_namei+0x117/0x3e0
Dec 11 04:03:56 fendrian kernel:  [filp_open+46/96] filp_open+0x2e/0x60
Dec 11 04:03:56 fendrian kernel:  [sys_open+59/112] sys_open+0x3b/0x70
Dec 11 04:03:56 fendrian kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Dec 11 04:03:56 fendrian kernel: 

    Daniel

-- 
> I have no life, and I must scream.
And in response, thus spake the Oracle:
} And there we have it, modern music summed up in one tidy sentence.

             reply	other threads:[~2003-12-10 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 22:19 Daniel Pittman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-06 22:02 Jonathan R. Hudson
2001-10-06 22:14 ` Alan Cox

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=87smjsgvtg.fsf@enki.rimspace.net \
    --to=daniel@rimspace.net \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: VFS: brelse: Trying to free free buffer' \
    /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

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).