> 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... Thanks, Andy -- Andrew W. Elble aweits@xxxxxxxxxxxxxxxxxx Infrastructure Engineer, Communications Technical Lead Rochester Institute of Technology PGP: BFAD 8461 4CCF DC95 DA2C B0EB 965B 082E 863E C912 -- 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
