From: Aaron Tomlin <atomlin@redhat.com>
To: mcgrof@kernel.org, christophe.leroy@csgroup.eu
Cc: linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
atomlin@atomlin.com, oleksandr@natalenko.name, neelx@redhat.com
Subject: [PATCH v2 0/3] module: Show the last unloaded module's taint flag(s)
Date: Thu, 14 Jul 2022 16:39:30 +0100 [thread overview]
Message-ID: <20220714153933.2095776-1-atomlin@redhat.com> (raw)
Hi Luis, Christophe,
In addition to the previous iteration, since this particular series does
indeed modify last_unloaded_module, I decided to use strscpy() as a
replacement for the now deprecated strlcpy().
Changes since v1 [1][2]:
- Replaced the deprecated strlcpy() for strscpy()
- Replaced last_unloaded_module[] with an anonymous structure
i.e. last_unloaded_module.name and last_unloaded_module.taints
- Ensured we modify last_unloaded_module.taints only when required
[1]: https://lore.kernel.org/lkml/20220627164052.2416485-1-atomlin@redhat.com/
[2]: https://lore.kernel.org/lkml/20220627164052.2416485-2-atomlin@redhat.com/
Aaron Tomlin (3):
module: Modify module_flags() to accept show_state argument
module: Use strscpy() for last_unloaded_module
module: Show the last unloaded module's taint flag(s)
kernel/module/internal.h | 2 +-
kernel/module/main.c | 27 ++++++++++++++++++---------
kernel/module/procfs.c | 2 +-
3 files changed, 20 insertions(+), 11 deletions(-)
--
2.34.3
next reply other threads:[~2022-07-14 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 15:39 Aaron Tomlin [this message]
2022-07-14 15:39 ` [PATCH v2 1/3] module: Modify module_flags() to accept show_state argument Aaron Tomlin
2022-07-14 15:39 ` [PATCH v2 2/3] module: Use strscpy() for last_unloaded_module Aaron Tomlin
2022-07-14 15:39 ` [PATCH v2 3/3] module: Show the last unloaded module's taint flag(s) Aaron Tomlin
2022-07-15 0:43 ` [PATCH v2 0/3] " Luis Chamberlain
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=20220714153933.2095776-1-atomlin@redhat.com \
--to=atomlin@redhat.com \
--cc=atomlin@atomlin.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=neelx@redhat.com \
--cc=oleksandr@natalenko.name \
/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).