public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: 2.6.22.1 Oops in put_nfs_open_context
Date: Thu, 23 Aug 2007 10:41:35 +0100	[thread overview]
Message-ID: <20070823094135.GE16743@gallifrey> (raw)
In-Reply-To: <20070807125938.GB30370@gallifrey>

* Dr. David Alan Gilbert (linux@treblig.org) wrote:
> * Trond Myklebust (trond.myklebust@fys.uio.no) wrote:
> > On Mon, 2007-08-06 at 11:01 -0700, Andrew Morton wrote:
> > > On Mon, 6 Aug 2007 11:08:13 +0100 "Dr. David Alan Gilbert" <linux@treblig.org> wrote:
> > > 
> > > >   The oops below is from one of a pair of machines that run compiles;
> > > > they're not managing to stay up for more than a day or two at a time
> > > > this is the first time I've actually managed to capture an oops from one.
> > > > They lock to the point where they still ping, and they won't toggle
> > > > capslock.  A top left running on them showed it sitting with pdflush
> > > > using 99% CPU.
> 
> <snip>
> 
> > > 
> > > We did a list operation on an already-deleted list_head.
> > > 
> > > That code has changed a lot between 2..22 and 2.6.23-rc2.  Hopefully for the
> > > better, although I can't immediately find a commit in there which looks like
> > > it addresses this bug.
> > 
> > I believe this fix should address it.
> 
> OK, I've got 2.6.23-rc2 with that patch up and running on one of the
> boxes; we'll see how long it survives.

Hi Trond,
  Just to confirm that the patch seems to have done the trick;
the machine in question has survived for a little over 2 weeks now
(which is probably a record for that machine).

Can you confirm whether that fix is actually in the latest 2.6.23 rc
or any of the 2.6.22 updates?

Thanks,

Dave
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

      reply	other threads:[~2007-08-23  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 10:08 2.6.22.1 Oops in put_nfs_open_context Dr. David Alan Gilbert
2007-08-06 18:01 ` Andrew Morton
2007-08-06 18:19   ` Trond Myklebust
2007-08-06 18:45     ` Andrew Morton
2007-08-06 19:38       ` Trond Myklebust
2007-08-07 12:59     ` Dr. David Alan Gilbert
2007-08-23  9:41       ` Dr. David Alan Gilbert [this message]

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=20070823094135.GE16743@gallifrey \
    --to=linux@treblig.org \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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