From: Chris Wedgwood <cw@f00f.org>
To: L A Walsh <lkml@tlinx.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>, linux-xfs@oss.sgi.com
Subject: Re: 2.6.7-vanilla-SMP kernel: pagebuf_get: failed to lookup pages
Date: Wed, 21 Jul 2004 17:33:57 -0700 [thread overview]
Message-ID: <20040722003357.GA31163@taniwha.stupidest.org> (raw)
In-Reply-To: <40FF0885.7060704@tlinx.org>
On Wed, Jul 21, 2004 at 05:21:25PM -0700, L A Walsh wrote:
> Will this be included/fixed in 2.6.8?
i assume that's the intention but i don't know when 2.6.8 is and how
much time the sgi people have before then. my guess is yes though
> How serious is the problem? The system doesn't seem to panic or
> indicate backup failures.
not sure, hch can you comment here maybe?
> Setting up a CVS tree to get a patch for a "stable-series" kernel
> seems a bit unstable.
CVS is "stable linux releases + XFS fixes" --- it's really not that
bad (whilst i personally don't use it, my tree is derieved from it and
i don't have problems)
> I'm not sure what I'd pull in besides the fix or even if I'd pull
> down a coherent/stable CVS image if I downloaded in the middle of
> when some other patch was being checked in.
cd path/to/workarea
cvs -qz9 -d :pserver:cvs@oss.sgi.com:/cvs co linux-2.6-xfs
cd linux-2.6-xfs
cp path/to/old/.config .config
make oldconfig
make ...
> Maybe I'm sounding like a wimp, but the idea of pulling in freshly
> checked in CVS code for use on a 'stable' machine is bordering on my
> discomfort zone. :-)
FWIW, the CVS tree isn't freshly checked in, it's a reflection of the
internal ptools tree where in theory you shouldn't get adhoc checkins
like lots of places (but yeah, it does sometimes break but not usually
badly).
Anyhow, if you don't like it you can (1) ingnore the problems (2) use
official binary releases from vendors (3) use ext3, etc.
whatever works for you...
--cw
next prev parent reply other threads:[~2004-07-22 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 0:04 L A Walsh
2004-07-22 0:12 ` Chris Wedgwood
2004-07-22 0:21 ` L A Walsh
2004-07-22 0:33 ` Chris Wedgwood [this message]
2004-07-29 5:54 ` 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=20040722003357.GA31163@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lkml@tlinx.org \
/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
all inboxes | Powered by JetHome®