From: David Ford <david@linux.com>
To: Blizbor <tb670725@ima.pl>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org, alan@redhat.org
Subject: Re: VFS: brelse message in syslog, its due to ReiserFS or kernelfailure ?
Date: Tue, 28 Nov 2000 06:29:50 -0800 [thread overview]
Message-ID: <3A23C15E.8A95D729@linux.com> (raw)
In-Reply-To: <5.0.0.25.0.20001128142121.01da9e20@195.117.13.2>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
I can't say who's fault it is, but I suggest this test12-pre2 patch for clarity
--- fs/buffer.c~ Tue Nov 28 05:11:56 2000
+++ fs/buffer.c Tue Nov 28 06:27:05 2000
@@ -1133,7 +1133,7 @@
atomic_dec(&buf->b_count);
return;
}
- printk("VFS: brelse: Trying to free free buffer\n");
+ printk("VFS: brelse: Trying to free already free buffer\n");
}
/*
Blizbor wrote:
> Machine: P3 500 on ASUS P2B, WD 15GB IDE drive.
> System RH7 with upgraded glibc.
>
> When I'm using 2.2.17 with ReiserFS:
> Nov 26 00:05:05 localhost kernel: Linux version 2.2.17 (root@localhost.localdomain) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 relea
> se)) #9 Sat Nov 25 17:09:40 CET 2000
>
> I have such messages in syslog and console:
> Nov 26 06:00:49 localhost kernel: VFS: brelse: Trying to free free buffer
> Nov 26 06:07:41 localhost kernel: VFS: brelse: Trying to free free buffer
> Nov 26 06:32:28 localhost kernel: VFS: brelse: Trying to free free buffer
[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 176 bytes --]
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard
next prev parent reply other threads:[~2000-11-28 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 13:29 VFS: brelse message in syslog, its due to ReiserFS or kernel failure ? Blizbor
2000-11-28 14:29 ` David Ford [this message]
2000-11-28 16:26 ` [reiserfs-list] " Chris Mason
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=3A23C15E.8A95D729@linux.com \
--to=david@linux.com \
--cc=alan@redhat.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=tb670725@ima.pl \
/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