| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <Pine.LNX.4.64.0710120814050.21625@localhost.localdomain> Date: Fri, 12 Oct 2007 08:18:30 -0400 (EDT) From: "Robert P. J. Day" <rpjday@...dspring.com> To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: what is the rationale for "TAINT_USER"? On Fri, 12 Oct 2007, Robert P. J. Day wrote: > > 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. 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 majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists