From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH v3 0/5] params: harden string ops and allocatio ops
Date: Mon, 20 Nov 2023 17:11:41 +0200 [thread overview]
Message-ID: <20231120151419.1661807-1-andriy.shevchenko@linux.intel.com> (raw)
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).
Changelog v3:
- added tags (Kees, Luis)
Changelog v2:
- dropped the s*printf() --> sysfs_emit() conversion as it revealed
an issue, i.e. reuse getters with non-page-aligned pointer, which
would be addressed separately
- added cover letter and clarified the possible route for the series
(Luis)
Andy Shevchenko (5):
params: Introduce the param_unknown_fn type
params: Do not go over the limit when getting the string length
params: Use size_add() for kmalloc()
params: Sort headers
params: Fix multi-line comment style
include/linux/moduleparam.h | 6 ++--
kernel/params.c | 56 ++++++++++++++++++++-----------------
2 files changed, 33 insertions(+), 29 deletions(-)
--
2.43.0.rc1.1.gbec44491f096
next reply other threads:[~2023-11-20 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 15:11 Andy Shevchenko [this message]
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 ` [PATCH v3 0/5] params: harden string ops and allocatio ops Andy Shevchenko
2023-12-01 17:43 ` 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=20231120151419.1661807-1-andriy.shevchenko@linux.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).