On Thu, Sep 1, 2022 at 11:57 AM Shuah Khan skhan@linuxfoundation.org wrote:
On 8/23/22 22:41, David Gow wrote:
On Wed, Aug 24, 2022 at 12:19 PM Joe Fradley joefradley@google.com wrote:
Commit c272612cb4a2 ("kunit: Taint the kernel when KUnit tests are run") added a new taint flag for when in-kernel tests run. This commit adds recognition of this new flag in kernel-chktaint.
What happens without this change? It isn't clear what this change is fixing.
Without this change the correct reason will not be displayed if the kernel is tainted because of a test.
Reviewed-by: David Gow davidgow@google.com Signed-off-by: Joe Fradley joefradley@google.com
Changes in v2:
- based off of kselftest/kunit branch
- Added David's Reviewed-by tag
This still looks good to me.
Unless anyone objects, I guess we'll take this through the KUnit branch (which, after all, is where the taint was originally added). I've added it to the list for 6.1, but it technically could be considered a fix for 6.0 as well.
I can definitely take this for Linux 6.0 with additional information on the problems seen without this change.
Great, thank you very much.
thanks, -- Shuah