[Top] [All Lists]

Re: [Bug 218] Probable mmap() bug that breaks cpp-3.2

To: Chris Wedgwood <cw@xxxxxxxx>
Subject: Re: [Bug 218] Probable mmap() bug that breaks cpp-3.2
From: Steve Lord <lord@xxxxxxx>
Date: 25 Feb 2003 16:00:03 -0600
Cc: bugzilla-daemon@xxxxxxxxxxx, xfs-master@xxxxxxxxxxx
In-reply-to: <20030225215141.GA22195@f00f.org>
References: <200302251918.h1PJI2LZ024311@oss.sgi.com> <20030225213859.GB22042@f00f.org> <1046209514.31698.2000.camel@jen.americas.sgi.com> <20030225215141.GA22195@f00f.org>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Tue, 2003-02-25 at 15:51, Chris Wedgwood wrote:
> On Tue, Feb 25, 2003 at 03:45:14PM -0600, Steve Lord wrote:
> > Nope, the problem was this filesystem was last running a kernel from
> > the time period where that bug was present. So there were a bunch of
> > files in this state. Running mapcheck cleaned up the filesystems,
> > and a new kernel cleaned up the bug.
> I'm confused.... i read it as, 'new kernel, will deadlock, mapcheck
> fixes this'.

Nope, old kernel created bad files, confused cpp in gcc 3.2, new kernel
does not generate these files. mapcheck fixes up old files/

> So I assumed I could store data past EOF and still confuse a new
> kernel.  I was wrong I take it?




Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx

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