mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Marc Dionne <marc.dionne@auristor.com>
Cc: Kenny Ho <Kenny.Ho@amd.com>, David Howells <dhowells@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	linux-afs@lists.infradead.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, y2kenny@gmail.com
Subject: Re: [PATCH] Remove hardcoded static string length
Date: Wed, 24 May 2023 18:01:42 +0200	[thread overview]
Message-ID: <c0fda91b-1e98-420f-a18a-16bbed25e98d@lunn.ch> (raw)
In-Reply-To: <CAB9dFdt4-cBFhEqsTXk9suE+Bw-xcpM0n3Q6rFmBaa+8A5uMWQ@mail.gmail.com>

> 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

  reply	other threads:[~2023-05-24 16:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 22:39 Kenny Ho
2023-05-24  0:49 ` Andrew Lunn
2023-05-24 15:43   ` Marc Dionne
2023-05-24 16:01     ` Andrew Lunn [this message]
2023-05-24 17:02       ` Kenny Ho
2023-05-24 17:43         ` Andrew Lunn
2023-05-24 18:01           ` Kenny Ho
2023-05-25  9:14             ` David Laight
2023-05-25 14:27               ` Kenny Ho
2023-05-25 15:04                 ` David Laight
2023-05-25 15:37                   ` Kenny Ho
2023-05-27 15:08                     ` Jeffrey E Altman
2023-05-29 13:32                       ` David Laight
2023-05-30 14:39                         ` Jeffrey E Altman
2023-05-27 14:45           ` Jeffrey E Altman
2023-05-27 15:08           ` Jeffrey E Altman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c0fda91b-1e98-420f-a18a-16bbed25e98d@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Kenny.Ho@amd.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=y2kenny@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®