public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	viro@parcelfarce.linux.theplanet.co.uk,
	Frank Cusack <fcusack@fcusack.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)
Date: 11 Jun 2003 19:47:24 +0200	[thread overview]
Message-ID: <shsn0goy09f.fsf@charged.uio.no> (raw)
In-Reply-To: <16103.26865.361044.360120@charged.uio.no>

>>>>> " " == 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

  reply	other threads:[~2003-06-11 17:34 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 23:54 nfs_refresh_inode: inode number mismatch Frank Cusack
2003-06-04 14:19 ` Trond Myklebust
2003-06-04 21:20   ` Frank Cusack
2003-06-04 21:28     ` Trond Myklebust
2003-06-05  9:11     ` Adrian Cox
2003-06-05  9:13       ` Russell King
2003-06-05 13:51         ` Trond Myklebust
2003-06-09 13:51 ` [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch) Frank Cusack
2003-06-09 13:55   ` Frank Cusack
2003-06-09 15:53   ` Linus Torvalds
2003-06-09 16:40     ` Trond Myklebust
2003-06-09 20:46       ` Frank Cusack
2003-06-10  0:01         ` Trond Myklebust
2003-06-11  0:54   ` viro
2003-06-11  1:28     ` Frank Cusack
2003-06-11  1:47       ` viro
2003-06-11  2:32         ` Frank Cusack
2003-06-11  2:37           ` viro
2003-06-11  1:59     ` Trond Myklebust
2003-06-11  2:27       ` viro
2003-06-11  2:43         ` Frank Cusack
2003-06-11  2:50           ` Frank Cusack
2003-06-11  3:00           ` viro
2003-06-11  7:22             ` [PATCH] NFS sillyrename fixes (was: [PATCH] nfs_unlink() race) Frank Cusack
2003-06-13  0:19               ` [PATCH] NFS sillyrename fixes take 3 Frank Cusack
2003-06-11  3:00         ` [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch) Trond Myklebust
2003-06-11  5:30     ` Linus Torvalds
2003-06-11  6:16       ` Andreas Dilger
2003-06-11 12:33       ` Alan Cox
2003-06-11 15:08         ` Linus Torvalds
2003-06-11 15:51           ` Alan Cox
2003-06-11 16:11             ` Linus Torvalds
2003-06-11 16:21               ` Alan Cox
2003-06-11 16:31                 ` Linus Torvalds
2003-06-11 16:34                   ` viro
2003-06-11 17:22                   ` Alan Cox
2003-06-11 17:37                     ` Trond Myklebust
2003-06-11 17:47                       ` Trond Myklebust [this message]
2003-06-12 21:59                         ` Jan Harkes
     [not found]                       ` <16103.29804.198545.680701@charged.uio.no>
2003-06-11 22:24                         ` Frank Cusack
2003-06-11 23:16                           ` Trond Myklebust
2003-06-11 23:35                             ` [PATCH] nfs_unlink() race Frank Cusack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=shsn0goy09f.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=fcusack@fcusack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox