Re: [PATCH] Revert "driver core: add TAINT_FORCED_BIND for when userspace manually messes with devices and drivers"

[Danilo Krummrich]

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!