[OpenAFS-devel] Re: Cache corruption with RX busy code

Andrew Deason adeason@sinenomine.net
Thu, 18 Apr 2013 16:21:59 -0500


On Thu, 18 Apr 2013 12:47:36 -0400
chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil> wrote:

> > We have the CID and epoch, too. I meant all of that in the context
> > of the relevant connection, which we can identify.
> 
> I don't think the client is sent back its own epoch, but rather the
> epoch for the server.   And I still believe a connection id collision
> is possible, but yes, very unlikely.

We know what conn and call channel the BUSY is for... we already
identify that now, to flag the call channel as busy on the client.

-- 
Andrew Deason
adeason@sinenomine.net