From: Nick Desaulniers <ndesaulniers@google.com>
To: Kees Cook <keescook@chromium.org>
Cc: Nathan Chancellor <nathan@kernel.org>, Tom Rix <trix@redhat.com>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [PATCH 3/3] HID: avoid runtime call to strlen
Date: Tue, 30 Aug 2022 13:53:09 -0700 [thread overview]
Message-ID: <20220830205309.312864-4-ndesaulniers@google.com> (raw)
In-Reply-To: <20220830205309.312864-1-ndesaulniers@google.com>
While looking into a CONFIG_FORTIFY=y related bug, I noticed that
hid_allocate calls strlen() on a local C string variable. This variable
can only have literal string values. There is no benefit to having
FORTIFY have this be a checked strlen call, because these are literal
values. By calling strlen() explicitly in the branches of a switch, the
compiler can evaluate strlen("literal value") at compile time, rather
than at runtime.
Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
---
drivers/hid/hid-input.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
index 48c1c02c69f4..9ad3cc88c26b 100644
--- a/drivers/hid/hid-input.c
+++ b/drivers/hid/hid-input.c
@@ -1922,12 +1922,15 @@ static struct hid_input *hidinput_allocate(struct hid_device *hid,
switch (application) {
case HID_GD_KEYBOARD:
suffix = "Keyboard";
+ suffix_len = strlen(suffix);
break;
case HID_GD_KEYPAD:
suffix = "Keypad";
+ suffix_len = strlen(suffix);
break;
case HID_GD_MOUSE:
suffix = "Mouse";
+ suffix_len = strlen(suffix);
break;
case HID_DG_PEN:
/*
@@ -1938,36 +1941,44 @@ static struct hid_input *hidinput_allocate(struct hid_device *hid,
* will have to change it and the test suite will not be happy.
*/
suffix = "Stylus";
+ suffix_len = strlen(suffix);
break;
case HID_DG_STYLUS:
suffix = "Pen";
+ suffix_len = strlen(suffix);
break;
case HID_DG_TOUCHSCREEN:
suffix = "Touchscreen";
+ suffix_len = strlen(suffix);
break;
case HID_DG_TOUCHPAD:
suffix = "Touchpad";
+ suffix_len = strlen(suffix);
break;
case HID_GD_SYSTEM_CONTROL:
suffix = "System Control";
+ suffix_len = strlen(suffix);
break;
case HID_CP_CONSUMER_CONTROL:
suffix = "Consumer Control";
+ suffix_len = strlen(suffix);
break;
case HID_GD_WIRELESS_RADIO_CTLS:
suffix = "Wireless Radio Control";
+ suffix_len = strlen(suffix);
break;
case HID_GD_SYSTEM_MULTIAXIS:
suffix = "System Multi Axis";
+ suffix_len = strlen(suffix);
break;
default:
+ suffix_len = 0;
break;
}
}
if (suffix) {
name_len = strlen(hid->name);
- suffix_len = strlen(suffix);
if ((name_len < suffix_len) ||
strcmp(hid->name + name_len - suffix_len, suffix)) {
hidinput->name = kasprintf(GFP_KERNEL, "%s %s",
--
2.37.2.672.g94769d06f0-goog
next prev parent reply other threads:[~2022-08-30 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 20:53 [PATCH 0/3] Fix FORTIFY=y UBSAN_LOCAL_BOUNDS=y Nick Desaulniers
2022-08-30 20:53 ` [PATCH 1/3] fortify: use __builtin_dynamic_object_size in __compiletime_strlen Nick Desaulniers
2022-08-31 18:34 ` Kees Cook
2022-08-30 20:53 ` [PATCH 2/3] fortify: cosmetic cleanups to __compiletime_strlen Nick Desaulniers
2022-08-31 13:13 ` kernel test robot
2022-08-31 19:06 ` Kees Cook
2022-08-30 20:53 ` Nick Desaulniers [this message]
2022-08-31 6:05 ` [PATCH 3/3] HID: avoid runtime call to strlen Greg KH
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=20220830205309.312864-4-ndesaulniers@google.com \
--to=ndesaulniers@google.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=trix@redhat.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