From: patchwork-bot+linux-riscv@kernel.org
To: <shao.mingyin@zte.com.cn>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
mikey@neuling.org, jiangfeng@kylinos.cn, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
linux-kernel@vger.kernel.org, zhang.yue5@zte.com.cn,
david.laight.linux@gmail.com, qingfang.deng@linux.dev
Subject: Re: [PATCH v4] riscv: lib: Fix ZBB strnlen wrap-around regression on huge counts
Date: Mon, 05 Oct 2026 17:00:13 +0000 [thread overview]
Message-ID: <179121961336.1813719.13062784666984813861.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915152656708z04s4oSYY2BGj34F36RZa@zte.com.cn>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:
On Tue, 15 Sep 2026 15:26:56 +0800 (CST) you wrote:
> From: Shao Mingyin <shao.mingyin@zte.com.cn>
>
> The aligned scan boundary is derived from the last valid byte,
> (s + count - 1). When count is huge (e.g. SIZE_MAX, which FORTIFY
> strcat/strlcat pass when the destination size is not known at compile
> time), s + count wraps around and the boundary lands before s, so the
> ZBB path returns a bogus length. The original implementation
> (5ba15d419fab) had the same wrap-around in its (s + count) & ~7
> boundary computation; after 5d588c684833 the wrapped boundary is caught
> by the pre-loop guard "bgeu t0, t4, 2f", which then always exits for
> aligned strings of 8 or more characters and strnlen() returns 8
> instead of the real length.
>
> [...]
Here is the summary with links:
- [v4] riscv: lib: Fix ZBB strnlen wrap-around regression on huge counts
https://git.kernel.org/riscv/c/d3b055d5d168
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-05 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:26 shao.mingyin
2026-09-22 3:48 ` Troy Mitchell
2026-09-25 20:54 ` Aurelien Jarno
2026-09-28 3:27 ` shao.mingyin
2026-09-28 3:35 ` shao.mingyin
2026-10-05 17:13 ` Paul Walmsley
2026-10-05 17:00 ` patchwork-bot+linux-riscv [this message]
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=179121961336.1813719.13062784666984813861.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=david.laight.linux@gmail.com \
--cc=jiangfeng@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mikey@neuling.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=qingfang.deng@linux.dev \
--cc=shao.mingyin@zte.com.cn \
--cc=zhang.yue5@zte.com.cn \
/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®