tainted-kernels.rst contains a small script to check which taint bits are set in /proc/sys/kernel/tainted. Add one more loop iteration to also handle the newly added TAINT_FORCED_BIND bit.
Also simplify by starting the loop at 0 and save substracting 1 for each usage of the loop counter. Acked-by: Randy Dunlap <[email protected]> Tested-by: Randy Dunlap <[email protected]> Fixes: fcbfaffee51a ("driver core: add TAINT_FORCED_BIND for when userspace manually messes with devices and drivers") Signed-off-by: Uwe Kleine-König <[email protected]> --- Documentation/admin-guide/tainted-kernels.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/admin-guide/tainted-kernels.rst b/Documentation/admin-guide/tainted-kernels.rst index abbf5e3dd749..a208811ad525 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 20); do echo $(($i-1)) $(($(cat /proc/sys/kernel/tainted)>>($i-1)&1));done + $ for i in $(seq 0 20); do echo $i $(($(cat /proc/sys/kernel/tainted)>>$i&1));done Table for decoding tainted state ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.47.3
