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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 7 Dec 2007 13:14:34 -0500
From:	Shane <>
To:	"Andrew Morton" <>
	"Trond Myklebust" <>,
	"J. Bruce Fields" <>,
	"Rafael J. Wysocki" <>
Subject: Re: 2.6.24-rc3-git4 NFS crossmnt regression

On Dec 7, 2007 7:02 AM, Andrew Morton <> wrote:
> > 2.6.24-rc3-git1 is last known good kernel. The problem also exists
> > with the latest snap 2.6.24-rc4-git4. NFS server is 2.6.23-rc9 and
> > is unchanged.
> hm, there have been no nfs changes since 2.6.24-rc4.

Ok, but the problem seems to have appeared before 2.6.24-rc4.

> > It is easily reproducible here, hopefully for the person who
> > knows how to debug it too :)
> >
> I guess a full set of the commands which you typed to reproduce this would
> help.

Server is 2.6.23-rc9 and is exporting:


The NFS client (Core2 SMP) 2.6.24-rc3-git4:

NFS-server:/dirA/dirB     /dirA/dirB    nfs

Then on the client when the new kernel has booted:

ls /dirA/dirB      --> normal listing
ls /dirA/dirB/dirC   -->  Stale NFS file handle
ls /dirA/dirB/dirD   -->  Stale NFS file handle

I will do a few more builds/boots and check -rc3-git2 and -rc3-git3.

Will report back shortly,

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists