[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aX3Q3O8qEasNeso8@smile.fi.intel.com>
Date: Sat, 31 Jan 2026 11:52:28 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Kees Cook <kees@...nel.org>
Cc: Feng Jiang <jiangfeng@...inos.cn>, palmer@...belt.com,
aou@...s.berkeley.edu, alex@...ti.fr, akpm@...ux-foundation.org,
andy@...nel.org, ebiggers@...nel.org, martin.petersen@...cle.com,
herbert@...dor.apana.org.au, samuel.holland@...ive.com,
ajones@...tanamicro.com, conor.dooley@...rochip.com,
charlie@...osinc.com, nathan@...nel.org, linusw@...nel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH v7 0/8] riscv: optimize string functions and add kunit
tests
On Fri, Jan 30, 2026 at 09:37:36AM -0800, Kees Cook wrote:
> On Fri, Jan 30, 2026 at 10:50:10AM +0800, Feng Jiang wrote:
> > This series provides optimized implementations of strnlen(), strchr(),
> > and strrchr() for the RISC-V architecture. The strnlen() implementation
> > is derived from the existing optimized strlen(). For strchr() and
> > strrchr(), the current versions use simple byte-by-byte assembly logic,
> > which will serve as a baseline for future Zbb-based optimizations.
>
> I'm happy with the Kunit elements here, so unless Andy has other
> feedback, please feel free to take this via the riscv tree. (Or if riscv
> maintainers would prefer, I can take it via string.)
I have an impression that I already gave some tag. Why aren't not here?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists