Re: 14 Jan 2021 08:25:36 GMT Breakage in RX Connection ID calculation

I'm  a bit confused about what versions are affected by this bug.  I've got mostly 1.8.[56] clients, which I'm upgrading now.  My servers are still running 1.6.22 and appear to be fine for vos operations between themselves, and the DB servers have been restarted since this happened (but not the fileservers).  Will I need to upgrade the servers too ?

And many thanks to everyone who jumped on debugging and fixing this.  It hadn't occurred to me that it was a generic problem until I saw that the mailing list had lit up.  I'd been trying to blame our network folks, as we usually do when really weird things happen (.
 
 Richard

On 2021-01-14, 13:21, "Jeffrey E Altman" <[email protected] on behalf of [email protected]> wrote:

    On 1/14/2021 10:55 AM, Jeffrey E Altman ([email protected]) wrote:
    > This morning at 14 Jan 2021 08:25:36 GMT all restarted or newly started
    > OpenAFS 1.8 clients and servers began to experience RX communication
    > failures.  The RX Connection ID of all calls initiated by the peer are
    > the same:
    > 
    >   0x80000002
    > 
    > Patches to correct the flaw are available from OpenAFS Gerrit
    > 
    >   https://gerrit.openafs.org/14491
    >   rx: rx_InitHost do not overwrite RAND_bytes rx_nextCid
    > 
    >   https://gerrit.openafs.org/14492
    >   rx: update_nextCid overflow handling is broken

    One more patch

      https://gerrit.openafs.org/14495
      rx: modify RX_CIDMASK to match update_nextCid()

    > Jeffrey Altman
    > AuriStor, Inc.