From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Andy Whitcroft <apw@canonical.com>,
Azeem Shaikh <azeemshaikh38@gmail.com>,
Brian Foster <bfoster@redhat.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Joe Perches <joe@perches.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
linux-bcachefs@vger.kernel.org, linux-hardening@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [GIT PULL] strlcpy removal for v6.8-rc1
Date: Fri, 19 Jan 2024 14:53:21 -0800 [thread overview]
Message-ID: <202401191450.CAF805687A@keescook> (raw)
In-Reply-To: <CAHk-=wj0j07B=n1Bt4EkDJpN5CBmxMuZhv+nnFdi0DxDVSiZAA@mail.gmail.com>
On Fri, Jan 19, 2024 at 02:00:14PM -0800, Linus Torvalds wrote:
> On Fri, 19 Jan 2024 at 13:14, Kees Cook <keescook@chromium.org> wrote:
> >
> > The kernel is now free of the strlcpy() API!
>
> .. still mentioned in docs and checkpatch. Maybe remove that too?
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).
If you feel like that's not right, I can either respin or send a
follow-up patch?
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-01-19 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 21:14 [GIT PULL] strlcpy removal for v6.8-rc1 Kees Cook
2024-01-19 21:38 ` Kent Overstreet
2024-01-19 22:00 ` Linus Torvalds
2024-01-19 22:53 ` Kees Cook [this message]
2024-01-19 23:59 ` Linus Torvalds
2024-01-19 22:50 ` pr-tracker-bot
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=202401191450.CAF805687A@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=apw@canonical.com \
--cc=azeemshaikh38@gmail.com \
--cc=bfoster@redhat.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.