linux-kernel - Re: [GIT PATCH] UIO patches for 2.6.21

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1177792297.7646.297.camel@localhost.localdomain>
Date:	Sat, 28 Apr 2007 22:31:37 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Hans-Jürgen Koch <hjk@...utronix.de>,
	Bill Davidsen <davidsen@....com>, Greg KH <gregkh@...e.de>,
	Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Benedikt Spranger <b.spranger@...utronix.de>
Subject: Re: [GIT PATCH] UIO patches for 2.6.21

On Sat, 2007-04-28 at 21:15 +0100, Alan Cox wrote:
> > > I have a political question, if I have a user space driver, is my kernel 
> > > tainted or not? 
> > 
> > Surely not. By using the kernel's userspace interface, you create no
> > "derived work" of the kernel. See COPYING in the root directory of the 
> > kernel sources for details.
> 
> That only covers normal system calls - but I don't think thats what is
> relevant, taints are for debug assistance not politics.
> 
> I think we should have a taint flag for UIO type drivers. Not for any
> licensing or political reason but for the simple fact it means that there
> may be other complexities to debugging - and not the same one as a binary
> module. Probably we want the same marker for mmap /dev/mem too.

I agree, if we make it entirely clear that the flag is nonpolitical. 

	tglx


-
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/