On Fri, Mar 19, 2021 at 05:09:22PM -0400, J. Bruce Fields wrote: > On Sat, Mar 20, 2021 at 07:48:44AM +1100, NeilBrown wrote: > > For NFSv4.1, only the EXCHANGE_ID is duplicate. There is only one > > CREATE_SESSION, and that is where the client is confirmed. So only one > > confirmed client. > > > > For NFSv4.0 bother SETCLIENTID and SETCLIENDID_CONFIRM are duplicate. > > So maybe both clients get confirmed. I should check that. > > Drifting off topic, but I don't see how this client behavior makes > sense. Mount is chatty enough without the unnecessary duplication. > Looking at the code.... I spent a little time tracing through the code and couldn't figure out what's going on. Just a note for the future that it'd be worth figuring out why the client is repeating SETCLIENTID+SETCLIENTID_CONFIRM or EXCHANGE_ID+CREATE_SESSION. I understand why it might be needed for trunking detection when there are multiple addresses involved, but otherwise it seems unnecessary. --b.
