From: cp0613@linux.alibaba.com
To: opensbi@lists.infradead.org
Cc: anup@brainfault.org, guoren@kernel.org,
Chen Pei <cp0613@linux.alibaba.com>
Subject: [PATCH 2/2] lib: Fix sbi_strchr to correctly handle null terminator search
Date: Fri, 6 Mar 2026 17:44:25 +0800 [thread overview]
Message-ID: <20260306094425.1918-3-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <20260306094425.1918-1-cp0613@linux.alibaba.com>
From: Chen Pei <cp0613@linux.alibaba.com>
The original sbi_strchr implementation did not conform to the C standard
behavior. According to the C standard and POSIX specification, strchr(s, 0)
should return a pointer to the null terminator at the end of string s.
The previous implementation used a while loop that would terminate when
either reaching the end of string or finding the character, but it would
return NULL when searching for the null terminator instead of returning
a pointer to the null terminator itself.
The fixed implementation uses a do-while loop that ensures even when
searching for the null terminator, the function correctly returns a
pointer to the null terminator position rather than NULL.
This fix ensures sbi_strchr behavior aligns with standard library
function semantics, making it more predictable and safe for users
expecting standard C library behavior.
Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
---
lib/sbi/sbi_string.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/lib/sbi/sbi_string.c b/lib/sbi/sbi_string.c
index f4f13942..3a10c254 100644
--- a/lib/sbi/sbi_string.c
+++ b/lib/sbi/sbi_string.c
@@ -88,13 +88,12 @@ char *sbi_strncpy(char *dest, const char *src, size_t count)
char *sbi_strchr(const char *s, int c)
{
- while (*s != '\0' && *s != (char)c)
- s++;
+ do {
+ if (*s == (char)c)
+ return (char *)s;
+ } while (*s++ != '\0');
- if (*s == '\0')
- return NULL;
- else
- return (char *)s;
+ return NULL;
}
char *sbi_strrchr(const char *s, int c)
--
2.50.1
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
next prev parent reply other threads:[~2026-03-06 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 9:44 [PATCH 0/2] Add string test to SBI unit test suite cp0613
2026-03-06 9:44 ` [PATCH 1/2] lib: tests: Add test for string cp0613
2026-03-06 9:44 ` cp0613 [this message]
2026-04-06 12:29 ` [PATCH 0/2] Add string test to SBI unit test suite Anup Patel
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=20260306094425.1918-3-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=anup@brainfault.org \
--cc=guoren@kernel.org \
--cc=opensbi@lists.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