From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Johan Hovold <johan@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
driver-core@lists.linux.dev, linux-trace-kernel@vger.kernel.org,
Leon Romanovsky <leon@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Michal Pecio <michal.pecio@gmail.com>
Subject: Re: [PATCH] Revert "driver core: add TAINT_FORCED_BIND for when userspace manually messes with devices and drivers"
Date: Fri, 30 Oct 2026 11:12:49 +0100 [thread overview]
Message-ID: <auRs-6y8ox4EWDcS@monoceros> (raw)
In-Reply-To: <DMHL9O0EWLKU.3F47YHYEGNURK@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
Hello Danilo,
On Thu, Oct 29, 2026 at 09:02:35PM +0100, Danilo Krummrich wrote:
> On Thu Oct 29, 2026 at 6:39 PM CET, Uwe Kleine-König wrote:
> > It's not part of commit fcbfaffee51a452cc8efcbaa3b88ec4595678424, but
> > conceptually we need
> >
> > diff --git a/Documentation/admin-guide/tainted-kernels.rst b/Documentation/admin-guide/tainted-kernels.rst
> > index 3d312bc17942..fcb8b9734548 100644
> > --- a/Documentation/admin-guide/tainted-kernels.rst
> > +++ b/Documentation/admin-guide/tainted-kernels.rst
> > @@ -74,7 +74,7 @@ a particular type of taint. It's best to leave that to the aforementioned
> > script, but if you need something quick you can use this shell command to check
> > which bits are set::
> >
> > - $ for i in $(seq 0 20); do echo $i $(($(cat /proc/sys/kernel/tainted)>>$i&1));done
> > + $ for i in $(seq 0 19); do echo $i $(($(cat /proc/sys/kernel/tainted)>>$i&1));done
> >
> > Table for decoding tainted state
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > in this change which was fixed in commit f1850e443b0e ("docs:
> > admin-guide: Handle TAINT_FORCED_BIND when parsing
> > /proc/sys/kernel/tainted"), but that commit shouldn't be reverted as it
> > contains a simplification that we should keep.
>
> Fixed it up, thanks!
Thanks. Looking at a287f97d4256b5f5527f5b5a54f8ada55e1482c7:
Acked-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
Reviewed-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
(just in case you're still willing to rewrite the commit for adding
that).
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-10-30 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 13:42 [PATCH] Revert "driver core: add TAINT_FORCED_BIND for when userspace manually messes with devices and drivers" Greg Kroah-Hartman
2026-10-29 17:39 ` Uwe Kleine-König
2026-10-29 20:02 ` Danilo Krummrich
2026-10-30 10:12 ` Uwe Kleine-König [this message]
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=auRs-6y8ox4EWDcS@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=johan@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=michal.pecio@gmail.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--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