linux-kernel - Re: 2.6.22.1 Oops in put_nfs_open

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070823094135.GE16743@gallifrey>
Date:	Thu, 23 Aug 2007 10:41:35 +0100
From:	"Dr. David Alan Gilbert" <linux@...blig.org>
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	"J. Bruce Fields" <bfields@...ldses.org>
Subject: Re: 2.6.22.1 Oops in put_nfs_open_context

* Dr. David Alan Gilbert (linux@...blig.org) wrote:
> * Trond Myklebust (trond.myklebust@....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@...blig.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   |_______/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/