On Thu, Jan 21, 2016 at 02:30:42PM -0500, Andrew W Elble wrote: > > > Doesn't this mean that a compound like e.g.: > > > > PUTFH > > CLOSE > > OPEN > > > > would result in a return of true on the OPEN, if CLOSE was in must_allow > > but OPEN wasn't? (Because the above loop sets spo_must_allowed as soon > > as it hits the CLOSE.) > > Yes. A real-world example is DELEGRETURN with the Linux NFS client: > > PUTFH > GETATTR > DELEGRETURN > > GETATTR isn't in spo_must_allowed, but the whole compound request looks like > krb5i in a krb5 setting. Still digesting the rest of your replies... Ugh. So the client actually needs to allow random other ops in any compound containing an spo_must_allow'd operation? That doesn't seem right to me. --b. -- 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
