From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Trond Myklebust <trondmy@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re:
Date: Sun, 23 Feb 2014 19:04:09 +0100 (CET) [thread overview]
Message-ID: <1981701027.186711.1393178649862.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <94863747-3B23-4534-8990-F04F0C8D54DE@gmail.com>
----- Original Message -----
> From: "Trond Myklebust" <trondmy@gmail.com>
> To: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
> Cc: "Linux NFS Mailing List" <linux-nfs@vger.kernel.org>
> Sent: Sunday, February 23, 2014 5:41:26 PM
> Subject: Re:
>
>
> On Feb 23, 2014, at 11:22, tigran.mkrtchyan@desy.de wrote:
>
> > to me it's unclear, why a SETATTR always follows an OPEN, even in case of
> > EXCLUSIVE4_1. With this fix, I get desired behavior.
>
> Yes, but that fix risks incurring an NFS4ERR_INVAL from which we cannot
> recover because it does not include the mandatory check for the allowed set
> of attributes.
> Please see RFC5661 section 18.16.3 about the client side use of
> ‘suppattr_exclcreat’ .
Yes, I noticed, that client never query that attribute. I will check a
possibility to add a check for suppattr_exclcreat as well.
Tigran.
>
> Cheers,
> Trond
next prev parent reply other threads:[~2014-02-23 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 16:22 tigran.mkrtchyan
2014-02-23 16:22 ` [PATCH] nfs4: EXCLUSIVE4_1 should send file attrs with OPEN tigran.mkrtchyan
2014-02-23 16:41 ` Trond Myklebust
2014-02-23 18:04 ` Mkrtchyan, Tigran [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-13 14:55 Re: Amos Kalonzo
2017-02-23 15:09 Qin's Yanjun
2014-07-24 8:35 Richard Wong
2008-07-28 7:13 nfs-utils-1.1.3 released Steve Dickson
2008-08-01 13:15 ` (was: nfs-utils-1.1.3 released) Aníbal Monsalve Salazar
[not found] ` <20080802172529.GC30454@fieldses.org>
2008-08-03 12:37 ` Paul Collins
2008-08-03 15:10 ` J. Bruce Fields
2008-08-04 15:32 ` Chuck Lever
2008-08-04 20:55 ` Paul Collins
2008-08-05 15:20 ` Chuck Lever
2008-08-05 19:28 ` Bug#492970: " Rasmus Bøg Hansen
2008-08-06 16:21 ` Chuck Lever
2008-08-06 18:21 ` Sergey Bolshakov
2008-07-27 17:40 (unknown) Linus Torvalds
2008-07-27 22:37 ` Trond Myklebust
2003-05-13 9:43 Emily
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=1981701027.186711.1393178649862.JavaMail.zimbra@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@gmail.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;
as well as URLs for NNTP newsgroup(s).