From: Nathan Scott <nathans@sgi.com>
To: Karol Kozimor <sziwan@hell.org.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5/2.6] buffer layer error at fs/buffer.c:2800 when unlinking
Date: Thu, 7 Aug 2003 09:59:08 +1000 [thread overview]
Message-ID: <20030806235908.GC854@frodo> (raw)
In-Reply-To: <20030803145113.GA31715@hell.org.pl>
On Sun, Aug 03, 2003 at 04:51:13PM +0200, Karol Kozimor wrote:
> Hi,
>
> I've recently managed to nail down the problems that have been occuring on
> my machine at least since 2.5.59. I use XFS as my rootfs, no other
> filesystems are compiled in, but I doubt the filesystem is to blame, since
> the problem does not appear under 2.4, despite the similar codebase.
> ...
> Here's the guts: upon unlinking files in /var/{run,lock/subsys} (typically
> during shutdown, but not only), and when doing "dd if=/dev/urandom
> of=/etc/random-seed count=1 bs=512" the following traces appear:
> #v+
> buffer layer error at fs/buffer.c:2800
> Call Trace:
> [<c014f1c6>] drop_buffers+0xb3/0xb9
> [<c014f208>] try_to_free_buffers+0x3c/0x96
> [<c01db1a1>] linvfs_release_page+0x74/0x78
> [<c014d2e6>] try_to_release_page+0x5c/0x6c
Hi there,
This is indeed an XFS issue (thanks for reporting it), the
patch below fixes it.
cheers.
--
Nathan
--- /usr/tmp/TmpDir.2013-0/linux/fs/xfs/linux/xfs_aops.c_1.45 2003-08-07 09:55:53.000000000 +1000
+++ linux/fs/xfs/linux/xfs_aops.c 2003-08-07 09:22:10.808194848 +1000
@@ -803,7 +803,7 @@
bh = bh->b_this_page;
} while (offset < end_offset);
- if (uptodate)
+ if (uptodate && bh == head)
SetPageUptodate(page);
if (startio)
next prev parent reply other threads:[~2003-08-07 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 14:51 [2.5/2.6] buffer layer error at fs/buffer.c:2800 when unlinking Karol Kozimor
2003-08-06 23:59 ` Nathan Scott [this message]
2003-08-10 22:16 ` Karol Kozimor
2003-08-11 0:34 ` Nathan Scott
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=20030806235908.GC854@frodo \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sziwan@hell.org.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.