public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: trond.myklebust@fys.uio.no
Cc: Andries Brouwer <aebr@win.tue.nl>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFS regression in 2.6
Date: Wed, 20 Aug 2003 12:02:44 -0700	[thread overview]
Message-ID: <3F43C5D4.9010704@redhat.com> (raw)
In-Reply-To: <16195.49464.935754.526386@charged.uio.no>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Trond Myklebust wrote:

> In short the scenario should be that
> 
>   - mkstemp() does an open(O_EXCL) -> nfs_lookup() creates hashed
>     negative dentry -> nfs_create() then does an O_EXCL call to the
>     server and instantiates the dentry.
> 
>   - unlink() walks the pathname -> finds the existing dentry using
>     cached_lookup() and only calls down to nfs_lookup_revalidate().

Sounds reasonable especially since the dup() call in my original example
isn't necessary.  So, the shortened test case is this:

#include <errno.h>
#include <error.h>
#include <stdlib.h>
#include <unistd.h>
int
main (void)
{
  char tmp[] = "estale-test.XXXXXX";
  int fd = mkstemp (tmp);
  if (fd == -1)
    error (EXIT_FAILURE, errno, "mkstemp failed");
  if (unlink (tmp) != 0)
    error (EXIT_FAILURE, errno, "unlink '%s' failed", tmp);
  if (ftruncate (fd, 0) != 0)
    error (EXIT_FAILURE, errno, "ftruncate failed");
  return 0;
}

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD4DBQE/Q8XU2ijCOnn/RHQRAtMYAJ9CgabR0FdQFG8Sobkrfv9aKloDmQCWN28G
QUj8oMiKWM7v61yupENQ+Q==
=fzKm
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-08-20 19:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 18:13 NFS regression in 2.6 Ulrich Drepper
2003-08-19 18:49 ` Ulrich Drepper
2003-08-19 19:19   ` Tupshin Harper
2003-08-19 19:06 ` Andries Brouwer
2003-08-19 19:15   ` Ulrich Drepper
2003-08-20  2:26     ` Andries Brouwer
2003-08-20  5:37 ` Trond Myklebust
2003-08-20 17:24   ` Andries Brouwer
2003-08-20 18:43     ` Trond Myklebust
2003-08-20 19:02       ` Ulrich Drepper [this message]
2003-08-20 19:52       ` Andries Brouwer
2003-08-20 20:02         ` Trond Myklebust
2003-08-21  0:28         ` NFS regression in 2.6 -- gnome problem Tupshin Harper
2003-08-21  0:38           ` Andries Brouwer
2003-08-21  1:07             ` Tupshin Harper
2003-08-21  3:05         ` NFS regression in 2.6 Ulrich Drepper
2003-08-20 17:43   ` Ulrich Drepper
2003-08-20 18:06     ` Andries Brouwer

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=3F43C5D4.9010704@redhat.com \
    --to=drepper@redhat.com \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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