linux-kernel - Re: NFSv4 client OOPS on 2.6.22-rc3

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: <1188350116.6701.249.camel@heimdal.trondhjem.org>
Date:	Tue, 28 Aug 2007 21:15:16 -0400
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	Harry Edmon <harry@...os.washington.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: NFSv4 client OOPS on 2.6.22-rc3 - I meant 2.6.23-rc3

On Wed, 2007-08-29 at 01:41 +0200, Michal Piotrowski wrote:
> Hi Harry,
> 
> On 28/08/07, Harry Edmon <harry@...os.washington.edu> wrote:
> > Typo in my last message - I meant 2.6.23-rc3, not 2.6.22-rc3.  Here it
> > is again with correction
> >
> > I had a kernel oops on my x86_64 dual quad-core Xeon system running
> > 2.6.23-rc3.  The system is an NFSv4 client to another 2.6.23-rc3
> > system.  The OOPS text is attached and the config file.
> >
> 
> Is this a regression? Does 2.6.22 work fine?

Yes and yes. It is due to a typo when I was working on correcting the
NFSv4 open() state tracking in 2.6.23-rc1. A patch is available and I'm
planning on merging it soon.

Trond

-
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/