xfs
[Top] [All Lists]

Re: TAKE - fix pagebuf locking bug

To: stimits@xxxxxxxxxx
Subject: Re: TAKE - fix pagebuf locking bug
From: Danny Cox <DCox@xxxxxxxxxxxxxx>
Date: Wed, 17 Jul 2002 08:04:20 -0400
Cc: XFS Mailing List <linux-xfs@xxxxxxxxxxx>
In-reply-to: <3D354483.8475F82F@idcomm.com>
References: <200207170228.g6H2SMd15531@jen.americas.sgi.com> <3D354483.8475F82F@idcomm.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Wed, 2002-07-17 at 06:18, D. Stimits wrote:
> Steve Lord wrote:
> > 
> > Modid:  2.4.x-xfs:slinx:123144a
> > linux/fs/xfs/pagebuf/page_buf.c - 1.40
> >         - fix unlock without lock bug in pagebuf, causes a BUG macro to trip
> >           also remove need for xfs_fs.h
> 
> Out of curiosity, how would this show up? I'm experimenting on a new

        If a BUG macro is tripped (executed) the kernel oopses.  It won't stall
(well, actually it will: forever ;-), but it'll present a message about
what went wrong, along with the C file and line number of the BUG macro,
plus the usual oops output.  Think of it as an abort() in kernel space,
but it can't, of course, dump core...yet.

-- 
kernel, n.: A part of an operating system that preserves the
medieval traditions of sorcery and black art.

Danny


<Prev in Thread] Current Thread [Next in Thread>