From: Alexey Dobriyan <adobriyan@gmail.com>
To: bp@suse.de
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org
Subject: [PATCH] x86, alternative: bump MAX_PATCH_LEN
Date: Mon, 14 Feb 2022 20:32:43 +0300 [thread overview]
Message-ID: <YgqSOyubItnEVRQK@localhost.localdomain> (raw)
Replacement instructions are raw data, there is no need to reserve
space for the NUL terminator.
Signed-off-by: Alexey Dobriyan (CloudLinux) <adobriyan@gmail.com>
---
arch/x86/kernel/alternative.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/x86/kernel/alternative.c
+++ b/arch/x86/kernel/alternative.c
@@ -35,7 +35,7 @@ int __read_mostly alternatives_patched;
EXPORT_SYMBOL_GPL(alternatives_patched);
-#define MAX_PATCH_LEN (255-1)
+#define MAX_PATCH_LEN 255
static int __initdata_or_module debug_alternative;
reply other threads:[~2022-02-14 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YgqSOyubItnEVRQK@localhost.localdomain \
--to=adobriyan@gmail.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).