[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c0fda91b-1e98-420f-a18a-16bbed25e98d@lunn.ch>
Date: Wed, 24 May 2023 18:01:42 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Marc Dionne <marc.dionne@...istor.com>
Cc: Kenny Ho <Kenny.Ho@....com>, David Howells <dhowells@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, linux-afs@...ts.infradead.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
y2kenny@...il.com
Subject: Re: [PATCH] Remove hardcoded static string length
> I don't think there is an RFC describing RX, but the closest thing to
> a spec (https://web.mit.edu/kolya/afs/rx/rx-spec) states:
>
> "If a server receives a packet with a type value of 13, and the
> client-initiated flag set, it should respond with a 65-byte payload
> containing a string that identifies the version of AFS software it is
> running."
>
> So while it may not actually cause any issues (the few things that
> look at the data just truncate past 65), it's probably best to keep
> the response at a fixed 65 bytes.
Thanks for the link and the quote.
So the compiler warning/error needs to be fixed a different want.
Andrew
---
pw-bot: cr
Powered by blists - more mailing lists