From: Kees Cook <keescook@chromium.org>
To: Azeem Shaikh <azeemshaikh38@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 0/2] kyber, blk-wbt: Replace strlcpy with strscpy
Date: Wed, 12 Jul 2023 16:44:44 -0700 [thread overview]
Message-ID: <202307121644.75BD707@keescook> (raw)
In-Reply-To: <20230703172159.3668349-1-azeemshaikh38@gmail.com>
On Mon, Jul 03, 2023 at 05:21:57PM +0000, Azeem Shaikh wrote:
> This patch series replaces strlcpy in the kyber and blk-wbt tracing subsystems wherever trivial
> replacement is possible, i.e return value from strlcpy is unused. The patches
> themselves are independent of each other and are applied to different subsystems. They are
> included as a series for ease of review.
>
> Note to reviewers: MAINTAINERS file does not specify clear ownership of
> these files so I have addressed these to the latest committer for these
> files: Jens Axboe <axboe@kernel.dk>.
>
> Azeem Shaikh (2):
> kyber: Replace strlcpy with strscpy
> blk-wbt: Replace strlcpy with strscpy
>
> include/trace/events/kyber.h | 8 ++++----
> include/trace/events/wbt.h | 8 ++++----
> 2 files changed, 8 insertions(+), 8 deletions(-)
These looks correct to me. I can take them if no one else wants them.
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
next prev parent reply other threads:[~2023-07-12 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 17:21 [PATCH 0/2] kyber, blk-wbt: Replace strlcpy with strscpy Azeem Shaikh
2023-07-03 17:21 ` [PATCH 1/2] kyber: " Azeem Shaikh
2023-07-03 17:21 ` [PATCH 2/2] blk-wbt: " Azeem Shaikh
2023-07-12 23:44 ` Kees Cook [this message]
2023-07-13 1:43 ` [PATCH 0/2] kyber, " Jens Axboe
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=202307121644.75BD707@keescook \
--to=keescook@chromium.org \
--cc=axboe@kernel.dk \
--cc=azeemshaikh38@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).