Linux Modules
 help / color / mirror / Atom feed
From: Bradley Morgan <brads@mainlining.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Daniel Gomez <da.gomez@kernel.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	Aaron Tomlin <atomlin@atomlin.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Aleksandr Nogikh <nogikh@google.com>,
	linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-usb@vger.kernel.org,
	driver-core@lists.linux.dev, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] module: fix up documentation for add_taint() and add_taint_module()
Date: Mon, 14 Sep 2026 15:42:37 +0100	[thread overview]
Message-ID: <066AC452-108A-45B4-A008-3FF84C85EAD6@mainlining.org> (raw)
In-Reply-To: <20260914-bind_taint-v4-2-eadf8a090903@linuxfoundation.org>

On 14 September 2026 15:30:32 BST, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>When add_taint_module() was added, the documentation for it was copied
>directly from add_taint().  But that documentation was a bit wrong
>(wrong variable name, and misleading boolean reference.)  Fix up both
>functions to have the correct documentation for how to use the
>lockdep_ok parameter to these functions.
>
>Reported-by: Petr Pavlu <petr.pavlu@suse.com>
>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>---
> kernel/module/main.c | 5 +++--
> kernel/panic.c       | 5 +++--
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
>diff --git a/kernel/module/main.c b/kernel/module/main.c
>index 444d990c9983..369794876c3e 100644
>--- a/kernel/module/main.c
>+++ b/kernel/module/main.c
>@@ -197,8 +197,9 @@ static inline int strong_try_module_get(struct module *mod)
>  * @flag: one of the TAINT_* constants.
>  * @lockdep_ok: whether lock debugging is still OK.
>  *
>- * If something bad has gone wrong, you'll want @lockdebug_ok = false, but for
>- * some noteworthy-but-not-corrupting cases, it can be set to true.
>+ * If something bad has gone wrong, you'll want
>+ * @lockdep_ok = LOCKDEP_NOW_UNRELIABLE, but for some
>+ * noteworthy-but-not-corrupting cases, it can be set to LOCKDEP_STILL_OK.
>  */
> void add_taint_module(struct module *mod, unsigned flag,
> 		      enum lockdep_ok lockdep_ok)
>diff --git a/kernel/panic.c b/kernel/panic.c
>index 213725b612aa..892045d8409e 100644
>--- a/kernel/panic.c
>+++ b/kernel/panic.c
>@@ -948,8 +948,9 @@ unsigned long get_taint(void)
>  * @flag: one of the TAINT_* constants.
>  * @lockdep_ok: whether lock debugging is still OK.
>  *
>- * If something bad has gone wrong, you'll want @lockdebug_ok = false, but for
>- * some notewortht-but-not-corrupting cases, it can be set to true.
>+ * If something bad has gone wrong, you'll want
>+ * @lockdep_ok = LOCKDEP_NOW_UNRELIABLE, but for some
>+ * noteworthy-but-not-corrupting cases, it can be set to LOCKDEP_STILL_OK.
>  */
> void add_taint(unsigned flag, enum lockdep_ok lockdep_ok)
> {
>
>
Reviewed-by: Bradley Morgan <brads@mainlining.org>

Thanks.
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/

  reply	other threads:[~2026-09-14 14:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 14:30 [PATCH v4 0/3] driver core: add TAINT_FORCED_BIND for when userspace manually messes with devices and drivers Greg Kroah-Hartman
2026-09-14 14:30 ` [PATCH v4 1/3] module: pull out add_taint_module() to be public Greg Kroah-Hartman
2026-09-14 14:38   ` sashiko-bot
2026-09-14 14:30 ` [PATCH v4 2/3] module: fix up documentation for add_taint() and add_taint_module() Greg Kroah-Hartman
2026-09-14 14:42   ` Bradley Morgan [this message]
2026-09-18 15:44   ` Aaron Tomlin
2026-09-14 14:30 ` [PATCH v4 3/3] driver core: add TAINT_FORCED_BIND for when userspace manually messes with devices and drivers Greg Kroah-Hartman
2026-09-14 14:43   ` sashiko-bot
2026-09-18 16:39 ` [PATCH v4 0/3] " Danilo Krummrich
2026-09-18 17:25   ` Greg Kroah-Hartman
2026-09-18 17:29     ` Bradley Morgan
2026-09-22  7:39   ` Uwe Kleine-König
2026-09-22 13:40     ` David Lechner
2026-09-22 21:04       ` Armin Wolf
2026-09-23  6:29         ` Uwe Kleine-König
2026-09-23  9:27         ` Greg Kroah-Hartman
2026-09-23  9:54           ` Uwe Kleine-König
2026-09-23 10:29             ` Greg Kroah-Hartman
2026-09-23 20:52           ` Armin Wolf

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=066AC452-108A-45B4-A008-3FF84C85EAD6@mainlining.org \
    --to=brads@mainlining.org \
    --cc=atomlin@atomlin.com \
    --cc=corbet@lwn.net \
    --cc=da.gomez@kernel.org \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mcgrof@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=nogikh@google.com \
    --cc=petr.pavlu@suse.com \
    --cc=rafael@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=samitolvanen@google.com \
    --cc=skhan@linuxfoundation.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