From: Josh Law <hlcj1234567@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Josh Law <objecting@objecting.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] lib/uuid: avoid double traversal in __uuid_parse()
Date: Thu, 12 Mar 2026 18:41:13 +0000 [thread overview]
Message-ID: <20260312184113.23564-1-objecting@objecting.org> (raw)
__uuid_parse() calls uuid_is_valid() to walk all 36 characters for
format validation, then walks the string a second time to parse the
hex bytes. Combine both passes into one: validate each hex digit
inline via hex_to_bin() return value and check the four dash positions
after the loop.
uuid_is_valid() remains exported unchanged for callers that only need
validation without parsing.
Signed-off-by: Josh Law <objecting@objecting.org>
---
lib/uuid.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/lib/uuid.c b/lib/uuid.c
index 128a51f1879b..89608f82ca6b 100644
--- a/lib/uuid.c
+++ b/lib/uuid.c
@@ -108,16 +108,20 @@ static int __uuid_parse(const char *uuid, __u8 b[16], const u8 ei[16])
static const u8 si[16] = {0,2,4,6,9,11,14,16,19,21,24,26,28,30,32,34};
unsigned int i;
- if (!uuid_is_valid(uuid))
- return -EINVAL;
-
for (i = 0; i < 16; i++) {
int hi = hex_to_bin(uuid[si[i] + 0]);
int lo = hex_to_bin(uuid[si[i] + 1]);
+ if (hi < 0 || lo < 0)
+ return -EINVAL;
+
b[ei[i]] = (hi << 4) | lo;
}
+ if (uuid[8] != '-' || uuid[13] != '-' ||
+ uuid[18] != '-' || uuid[23] != '-')
+ return -EINVAL;
+
return 0;
}
--
2.34.1
next reply other threads:[~2026-03-12 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 18:41 Josh Law [this message]
2026-03-12 20:48 ` [PATCH 3/3] lib/uuid: avoid double traversal in __uuid_parse() Andrew Morton
2026-03-12 20:51 ` Josh Law
2026-03-13 9:04 ` Andy Shevchenko
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=20260312184113.23564-1-objecting@objecting.org \
--to=hlcj1234567@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=objecting@objecting.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.