From: Kenny Ho <Kenny.Ho@amd.com>
To: David Howells <dhowells@redhat.com>,
Marc Dionne <marc.dionne@auristor.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>
Cc: Kenny Ho <Kenny.Ho@amd.com>
Subject: [PATCH] Remove hardcoded static string length
Date: Tue, 23 May 2023 18:39:44 -0400 [thread overview]
Message-ID: <20230523223944.691076-1-Kenny.Ho@amd.com> (raw)
UTS_RELEASE length can exceed the hardcoded length. This is causing
compile error when WERROR is turned on.
Signed-off-by: Kenny Ho <Kenny.Ho@amd.com>
---
net/rxrpc/local_event.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/rxrpc/local_event.c b/net/rxrpc/local_event.c
index 19e929c7c38b..61d53ee10784 100644
--- a/net/rxrpc/local_event.c
+++ b/net/rxrpc/local_event.c
@@ -16,7 +16,7 @@
#include <generated/utsrelease.h>
#include "ar-internal.h"
-static const char rxrpc_version_string[65] = "linux-" UTS_RELEASE " AF_RXRPC";
+static const char rxrpc_version_string[] = "linux-" UTS_RELEASE " AF_RXRPC";
/*
* Reply to a version request
--
2.25.1
next reply other threads:[~2023-05-23 22:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 22:39 Kenny Ho [this message]
2023-05-24 0:49 ` Andrew Lunn
2023-05-24 15:43 ` Marc Dionne
2023-05-24 16:01 ` Andrew Lunn
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=20230523223944.691076-1-Kenny.Ho@amd.com \
--to=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®