* Slava Pestov wrote:
> This helps when writing automated tests, since they can fail the
> test if the kernel was tainted instead of manually scraping dmesg
> for interesting strings.
>
> Signed-off-by: Slava Pestov
> ---
> include/linux/kernel.h | 1 +
> kernel/locking/lockdep.c | 31
On Thu, 29 Jan 2015 13:50:26 -0800 Slava Pestov wrote:
> This helps when writing automated tests, since they can fail the
> test if the kernel was tainted instead of manually scraping dmesg
> for interesting strings.
Seems sane. It wouldn't hurt to mention this in
Documentation/locking/lockdep-
This helps when writing automated tests, since they can fail the
test if the kernel was tainted instead of manually scraping dmesg
for interesting strings.
Signed-off-by: Slava Pestov
---
include/linux/kernel.h | 1 +
kernel/locking/lockdep.c | 31 +++
kernel/panic
Hi Peter and Ingo,
Something like this seems like it would be a useful addition. I've heard
a few people mention that lockdep taints the kernel and even seen it come
up in mailing list posts, but this does not appear to be the case.
This patch adds a new taint flag. I'm using a similar patch on 3
4 matches
Mail list logo
