mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: NIIBE Yutaka <gniibe@m17n.org>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client)
Date: Tue, 19 Mar 2002 15:45:38 +0100	[thread overview]
Message-ID: <E16nKrq-0007uP-00@charged.uio.no> (raw)
In-Reply-To: <shswuwkujx5.fsf@charged.uio.no> <15509.47571.248407.537415@charged.uio.no> <200203182357.g2INvIB13203@mule.m17n.org>

On Tuesday 19. March 2002 00:57, NIIBE Yutaka wrote:
> File handle must be unique.  But I think that it may be reused (for
> different type).  Client side cache should handle this case, IMO.

No...

>From RFC1094:
----------------
2.3.3.  fhandle

          typedef opaque fhandle[FHSIZE];

      The "fhandle" is the file handle passed between the server and the
      client.  All file operations are done using file handles to refer
      to a file or directory.  The file handle can contain whatever
      information the server needs to distinguish an individual file.
-----------------
IOW: the server is required to distinguish an individual file.

Note that there is no time limit on this: if I try to write to a file that 
was deleted behind my back, the server is supposed to be able to determine 
which file I was writing to.

This is further clarified in RFC1813:
-----------------
      If two file handles from the same server are equal, they must refer to
      the same file
------------------

Again: at no point does the RFC say that there is a timelimit on the above 
(unlike the so-called 'volatile filehandles' that were introduced for NFSv4)

Indeed if you think about it, then there is no way the RFC *can* allow the 
client to take the burden: we are talking about a stateless system. Unless 
the server has a way of notifying the client that a filehandle is invalid, 
and/or the file was deleted there is no way that the client can know...

Cheers,
  Trond

  reply	other threads:[~2002-03-19 14:46 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 12:19 Stephan von Krawczynski
2002-03-09 19:10 ` Alan Cox
2002-03-10 17:50 ` Stephan von Krawczynski
2002-03-10 22:39 ` Trond Myklebust
2002-03-11  0:18   ` Stephan von Krawczynski
2002-03-11  0:28   ` Trond Myklebust
2002-03-11  6:14     ` Oleg Drokin
2002-03-11 10:46     ` Stephan von Krawczynski
2002-03-11 10:52       ` Oleg Drokin
2002-03-11 11:24         ` Stephan von Krawczynski
2002-03-11 12:47         ` Stephan von Krawczynski
2002-03-11 12:59           ` Oleg Drokin
2002-03-15 11:02             ` Stephan von Krawczynski
2002-03-15 11:13               ` Oleg Drokin
2002-03-15 11:30             ` Stephan von Krawczynski
2002-03-15 11:36               ` Sean Neakums
2002-03-15 11:37               ` Oleg Drokin
2002-03-15 12:03               ` Stephan von Krawczynski
2002-03-15 12:05                 ` Oleg Drokin
2002-03-21 14:45                   ` Stephan von Krawczynski
2002-03-21 14:57                     ` Stephan von Krawczynski
2002-03-21 15:01                       ` Oleg Drokin
2002-03-21 15:05                         ` Stephan von Krawczynski
2002-03-21 15:07                           ` Oleg Drokin
2002-03-21 17:15                             ` Stephan von Krawczynski
2002-03-22  5:48                               ` Oleg Drokin
2002-03-22  0:19                     ` Trond Myklebust
2002-03-22 11:00                       ` Stephan von Krawczynski
2002-03-22 11:07                         ` Trond Myklebust
2002-03-22 13:19                           ` Stephan von Krawczynski
2002-03-15 14:07             ` Stephan von Krawczynski
2002-03-11 14:48         ` Stephan von Krawczynski
2002-03-11 13:51           ` Oleg Drokin
2002-03-11 14:03             ` Trond Myklebust
2002-03-11 15:57             ` Stephan von Krawczynski
2002-03-11 16:31               ` Hans Reiser
2002-03-15 10:32               ` Oleg Drokin
2002-03-11 13:59           ` Trond Myklebust
2002-03-11 11:00       ` Stephan von Krawczynski
2002-03-11 11:11         ` Oleg Drokin
2002-03-18  7:07     ` NIIBE Yutaka
2002-03-18  8:15       ` Trond Myklebust
2002-03-18  9:33         ` NIIBE Yutaka
2002-03-18  9:56           ` Trond Myklebust
2002-03-18 23:57             ` NIIBE Yutaka
2002-03-19 14:45               ` Trond Myklebust [this message]
2002-03-20  0:42                 ` NIIBE Yutaka
2002-03-20  8:30                   ` Trond Myklebust
2002-03-19 15:42             ` Ton Hospel
2002-03-19 18:31               ` BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and Alan Cox
2002-03-19 22:10               ` BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client) Trond Myklebust
2002-03-22 10:33                 ` David Woodhouse
2002-03-22 11:03                   ` Trond Myklebust

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=E16nKrq-0007uP-00@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=gniibe@m17n.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    /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

all inboxes | Powered by JetHome®