http://kerneltrap.org/node/6656
but it's not clear how it can possibly be set from userland given
that:
$ grep -r TAINT_USER *
include/linux/kernel.h:#define TAINT_USER (1<<6)
kernel/panic.c: tainted & TAINT_USER ? 'U' : ' ',
$
am i missing something screamingly obvious?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
#ifdef CONFIG_PROC_SYSCTL
{
.ctl_name = KERN_TAINTED,
.procname = "tainted",
.data = &tainted,
.maxlen = sizeof(int),
.mode = 0644,
.proc_handler = &proc_dointvec_taint,
},
#endif
Regards,
Nadia
>
> i can see what the theoretical purpose for it is here:
>
> http://kerneltrap.org/node/6656
>
> but it's not clear how it can possibly be set from userland given
> that:
>
> $ grep -r TAINT_USER *
> include/linux/kernel.h:#define TAINT_USER (1<<6)
> kernel/panic.c: tainted & TAINT_USER ? 'U' : ' ',
> $
>
> am i missing something screamingly obvious?
whoops, never mind -- if i read correctly, that particular flag bit
must be set *explicitly* when writing to /proc/sys/kernel/tainted. i
originally thought it would be set by kernel code simply by the act of
writing to /proc/sys/kernel/tainted, and i couldn't see where that was
happening. carry on.
Grepping for "tainted" leads me to:
echo 32 > /proc/sys/kernel/tainted
Björn
Oops, yeah, 64... And it didn't lead me to the exact phrase, but the
sysctl handler, which (implicitly) led me to that command. Sorry for
the confusion.