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 <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • NFSv4 client OOPS on 2.6.22-rc3 - I meant 2.6.23-rc3
    • From: Harry Edmon <[email protected]>
  • Re: NFSv4 client OOPS on 2.6.22-rc3 - I meant 2.6.23-rc3
    • From: "Michal Piotrowski" <[email protected]>

• Prev by Date: miss list_del(), bug ?
• Next by Date: [patch] i386, apic: fix 4 bit apicid assumption of mach-default
• Previous by thread: Re: NFSv4 client OOPS on 2.6.22-rc3 - I meant 2.6.23-rc3
• Next by thread: NFSv4 client OOPS on 2.6.22-rc3
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]