On Tue, 2008-09-23 at 08:59 +0100, Ian Campbell wrote:
quoted text
> I've found that the problem was backported into the stable stream since
> I cannot reproduce the issue with 2.6.26 but I can with 2.6.26.5. This
> is quite useful since there are only 3 relevant looking changesets in
> that range. I will bisect between these before confirming the culprit on
> mainline.

It reports:

        daedfbe2a67628a40076a6c75fb945c60f608a2e is first bad commit
        commit daedfbe2a67628a40076a6c75fb945c60f608a2e
        Author: Trond Myklebust <Trond.Myklebust@netapp.com>
        Date:   Wed Jun 11 17:39:04 2008 -0400
       =20
            NFS: Ensure we zap only the access and acl caches when setting =
new acls
           =20
            commit f41f741838480aeaa3a189cff6e210503cf9c42d upstream
           =20
            ...and ensure that we obey the NFS_INO_INVALID_ACL flag when re=
trieving the
            acls.
           =20
            Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
            Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

I'm just about to build f41f741838480aeaa3a189cff6e210503cf9c42d and the
one before and try those.

I'm not using ACLs as far as I am aware.

Ian.

--=20
Ian Campbell

If we were meant to get up early, God would have created us with alarm cloc=
ks.