[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHk-=whu2k-PwHVZS4uKj3kksVUF_Fqzap-YXwnVKeC6S9pBNg@mail.gmail.com>
Date: Fri, 19 Jan 2024 15:59:43 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Kees Cook <keescook@...omium.org>
Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
Andy Shevchenko <andy.shevchenko@...il.com>, Andy Whitcroft <apw@...onical.com>,
Azeem Shaikh <azeemshaikh38@...il.com>, Brian Foster <bfoster@...hat.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>, Joe Perches <joe@...ches.com>,
Kent Overstreet <kent.overstreet@...ux.dev>, linux-bcachefs@...r.kernel.org,
linux-hardening@...r.kernel.org, Lukas Bulwahn <lukas.bulwahn@...il.com>
Subject: Re: [GIT PULL] strlcpy removal for v6.8-rc1
On Fri, 19 Jan 2024 at 14:53, Kees Cook <keescook@...omium.org> wrote:
>
> Sorry, I should have called that out in the PR, but the commit itself
> had my rationale for intentionally leaving those in:
>
> Leave mentions in Documentation (about its deprecation), and in
> checkpatch.pl (to help migrate host-only tools/ usage).
Hmm. Yeah, I guess the host tooling is an issue, although there
strlcpy makes a lot more sense since I think it exists in various user
space libraries (while strscpy() is kernel-only).
> If you feel like that's not right, I can either respin or send a
> follow-up patch?
Oh, I already took the pull request, I was just reacting to leftovers.
This is not a big deal.
Linus
Powered by blists - more mailing lists