[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169047317156.2400214.7935379824991435172.b4-ty@chromium.org>
Date: Thu, 27 Jul 2023 08:52:53 -0700
From: Kees Cook <keescook@...omium.org>
To: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Azeem Shaikh <azeemshaikh38@...il.com>
Cc: Kees Cook <keescook@...omium.org>, linux-hardening@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf: Replace strlcpy with strscpy
On Mon, 03 Jul 2023 16:58:16 +0000, Azeem Shaikh wrote:
> strlcpy() reads the entire source buffer first.
> This read may exceed the destination size limit.
> This is both inefficient and can lead to linear read
> overflows if a source string is not NUL-terminated [1].
> In an effort to remove strlcpy() completely [2], replace
> strlcpy() here with strscpy().
> No return values were used, so direct replacement is safe.
>
> [...]
Applied, thanks!
[1/1] perf: Replace strlcpy with strscpy
https://git.kernel.org/kees/c/c9732f1461f9
Best regards,
--
Kees Cook
Powered by blists - more mailing lists