----- Original Message ----- > From: "Trond Myklebust" <trondmy@xxxxxxxxx> > To: "Tigran Mkrtchyan" <tigran.mkrtchyan@xxxxxxx> > Cc: "Linux NFS Mailing List" <linux-nfs@xxxxxxxxxxxxxxx> > Sent: Sunday, February 23, 2014 5:41:26 PM > Subject: Re: > > > On Feb 23, 2014, at 11:22, tigran.mkrtchyan@xxxxxxx 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 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
