Re: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)

• Next message: Jeff Garzik: "Re: [PATCH] And yet more PCI fixes for 2.5.70"
• Previous message: war: "Re: WESTERN DIGITAL 200GB IDE DRIVES GO OFFLINE - HOW TO FIX"
• In reply to: Trond Myklebust: "Re: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)"
• Next in thread: Jan Harkes: "Re: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)"
• Reply: Jan Harkes: "Re: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> " " == Trond Myklebust <trond.myklebust@fys.uio.no> writes:

> 2.4 has the 'return ESTALE if current dir fails d_revalidate()'
> test. Looks like the vfat stuff has the same problem that

I should learn to complete my own sentences before sending... The
above should read:

Looks like the vfat stuff has the same problem that Coda did. It is
unintentionally triggering the ESTALE code, as it assumes that
d_revalidate() is advisory only.

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/

• Next message: Jeff Garzik: "Re: [PATCH] And yet more PCI fixes for 2.5.70"
• Previous message: war: "Re: WESTERN DIGITAL 200GB IDE DRIVES GO OFFLINE - HOW TO FIX"
• In reply to: Trond Myklebust: "Re: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)"
• Next in thread: Jan Harkes: "Re: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)"
• Reply: Jan Harkes: "Re: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:28 EST