> Are you sure that you didn't mess up the fixups with
> 2.4.18-pre1? That might explain things, since you would be
> messing with nfs_refresh_inode. What you need to do against
> 2.4.18-pre1 is first to revert the patch
> linux-2.4.17-fattr.dif. After that you should be able to apply
> linux-2.4.17-NFS_ALL.dif directly without any rejections...
Please also note that the version of linux-2.4.17-NFS_ALL.dif that
appeared on my site dated prior to 20th December had a bug within
nfs_refresh_inode that cause corruption of file attributes.
Is it possible that you might be using this buggy version?
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/