From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3 0/5] params: harden string ops and allocatio ops
Date: Fri, 1 Dec 2023 17:51:07 +0200 [thread overview]
Message-ID: <ZWoA6w3A7f0CDYnu@smile.fi.intel.com> (raw)
In-Reply-To: <20231120151419.1661807-1-andriy.shevchenko@linux.intel.com>
On Mon, Nov 20, 2023 at 05:11:41PM +0200, Andy Shevchenko wrote:
> A couple of patches are for get the string ops, used in the module,
> slightly harden. On top a few cleanups.
>
> Since the main part is rather hardening, I think the Kees' tree is
> the best fit for the series. It also possible to route via Greg's
> sysfs (driver core?), but I'm open for another option(s).
Kees, Greg, can you apply this series?
Or should I do something about it?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-12-01 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 15:11 [PATCH v3 0/5] params: harden string ops and allocatio ops Andy Shevchenko
2023-11-20 15:11 ` [PATCH v3 1/5] params: Introduce the param_unknown_fn type Andy Shevchenko
2023-11-20 15:11 ` [PATCH v3 2/5] params: Do not go over the limit when getting the string length Andy Shevchenko
2023-11-20 15:11 ` [PATCH v3 3/5] params: Use size_add() for kmalloc() Andy Shevchenko
2023-11-20 15:11 ` [PATCH v3 4/5] params: Sort headers Andy Shevchenko
2023-11-20 15:11 ` [PATCH v3 5/5] params: Fix multi-line comment style Andy Shevchenko
2023-12-01 15:51 ` Andy Shevchenko [this message]
2023-12-01 17:43 ` [PATCH v3 0/5] params: harden string ops and allocatio ops Kees Cook
2023-12-01 19:05 ` Andy Shevchenko
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=ZWoA6w3A7f0CDYnu@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@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 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.