From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] seq_file: Replace strncpy()+nul by strscpy()
Date: Mon, 17 Jul 2023 19:05:44 +0300 [thread overview]
Message-ID: <ZLVm2FLCRSnlYVUC@smile.fi.intel.com> (raw)
In-Reply-To: <202307170826.397635AD@keescook>
On Mon, Jul 17, 2023 at 08:43:55AM -0700, Kees Cook wrote:
> On Mon, Jul 17, 2023 at 12:33:32PM +0300, Andy Shevchenko wrote:
...
> I think this doesn't need to use seq_show_option_n() at all.
Quite likely. Nevertheless, it's one of the dozens (?) warnings like this.
...
> Reviewed-by: Kees Cook <keescook@chromium.org>
Thank you for the review!
I think it's you who may take it as seq_file.h seems everybody's playground.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-07-17 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 9:33 [PATCH v1 1/1] seq_file: Replace strncpy()+nul by strscpy() Andy Shevchenko
2023-07-17 15:43 ` Kees Cook
2023-07-17 16:05 ` Andy Shevchenko [this message]
2023-07-17 22:58 ` Kees Cook
2023-07-17 23:09 ` Kees Cook
2023-07-19 5:00 ` Kees Cook
2023-07-19 5:26 ` Andy Shevchenko
2023-07-18 9:42 ` David Laight
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=ZLVm2FLCRSnlYVUC@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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