From: Peter Staubach <staubach@redhat.com>
To: Janne Karhunen <Janne.Karhunen@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFSv3 client reordering RENAMEs
Date: Thu, 15 Jun 2006 12:05:25 -0400 [thread overview]
Message-ID: <44918545.2090002@redhat.com> (raw)
In-Reply-To: <200606151754.33384.Janne.Karhunen@gmail.com>
Janne Karhunen wrote:
>On Thursday 15 June 2006 16:44, Peter Staubach wrote:
>
>
>
>>>really expect RENAME to be reordered as mv is generally considered
>>>atomic. That, and RFC 1813 mandates RENAME to be atomic. Is this a
>>>known thing and do you guys consider this feature or a bug?
>>>
>>>
>>Can you construct a testcase which exhibits this behavior?
>>
>>
>
>Possibly .. if someone first acks that this indeed would be
>considered as bug and not as a feature :/
>
Yes, I believe that this would be considered to be a bug...
ps
next prev parent reply other threads:[~2006-06-15 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 13:38 NFSv3 client reordering RENAMEs Janne Karhunen
2006-06-15 13:44 ` Peter Staubach
2006-06-15 14:54 ` Janne Karhunen
2006-06-15 16:05 ` Peter Staubach [this message]
2006-06-16 6:25 ` Janne Karhunen
2006-06-16 13:45 ` Peter Staubach
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=44918545.2090002@redhat.com \
--to=staubach@redhat.com \
--cc=Janne.Karhunen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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