From: Colin Ian King <colin.i.king@gmail.com>
To: Kees Cook <kees@kernel.org>, linux-hardening@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] fortify: add branch hints on unlikely fortify_panic paths
Date: Wed, 25 Jun 2025 17:12:20 +0100 [thread overview]
Message-ID: <20250625161221.295575-1-colin.i.king@gmail.com> (raw)
Analysis with gcov while running the stress-ng urandom stressor
shows that there are a couple of fortify panic paths that are highly
unlikely to be executed for well-behaving code. Adding appropriate
branch hints improves the stress-ng urandom stressor my a small
but statistically measureable amount. Ran 100 x 1 minute tests and
measured the stressor bogo-op rates on a Debian based Intel(R)
Core(TM) Ultra 9 285K with a 6.15 kernel with turbo disabled to
reduce jitter.
Results based on a Geometic Mean of 100 tests:
Without patch: 50512.95 bogo-ops/sec
With patch: 50819.58 bogo-ops/sec
%Std.Deviation of ~0.18%, so low jitter in results, improvement of ~0.6%
Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
include/linux/fortify-string.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/fortify-string.h b/include/linux/fortify-string.h
index e4ce1cae03bf..2ab8cb641d70 100644
--- a/include/linux/fortify-string.h
+++ b/include/linux/fortify-string.h
@@ -593,9 +593,9 @@ __FORTIFY_INLINE bool fortify_memcpy_chk(__kernel_size_t size,
* (The SIZE_MAX test is to optimize away checks where the buffer
* lengths are unknown.)
*/
- if (p_size != SIZE_MAX && p_size < size)
+ if (unlikely(p_size != SIZE_MAX && p_size < size))
fortify_panic(func, FORTIFY_WRITE, p_size, size, true);
- else if (q_size != SIZE_MAX && q_size < size)
+ else if (unlikely(q_size != SIZE_MAX && q_size < size))
fortify_panic(func, FORTIFY_READ, p_size, size, true);
/*
--
2.50.0
next reply other threads:[~2025-06-25 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 16:12 Colin Ian King [this message]
2025-06-27 0:14 ` kernel test robot
2025-06-27 1:05 ` kernel test robot
2025-06-27 16:36 ` Kees Cook
2025-06-27 16:47 ` Colin King (gmail)
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=20250625161221.295575-1-colin.i.king@gmail.com \
--to=colin.i.king@gmail.com \
--cc=kees@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®