linux-kernel - Re: [PATCH 2/3] UIO: Documentation

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] [day] [month] [year] [list]

Date:	Thu, 9 Aug 2007 18:50:10 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Greg KH" <gregkh@...e.de>
Cc:	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>,
	linux-kernel@...r.kernel.org, "Hans J. Koch" <hjk@...utronix.de>
Subject: Re: [PATCH 2/3] UIO: Documentation

On 09/08/07, Greg KH <gregkh@...e.de> wrote:
> On Thu, Aug 09, 2007 at 01:03:39AM +0200, Jesper Juhl wrote:
> > >
> > I think the only way to avoid it is to not provide something like UIO.
>
> Problem is, things like UIO provide a real solution for a wide range of
> different types of devices.  Like the one provided in the kernel right
> now, and a bunch of others that I am currently discussing with different
> manufacturers (think high-speed DSPs that just want to give userspace
> direct access to the card and have the kernel get the hell out of the
> way so data can be read and processed as fast as possible.)
>
Please understand that I'm not saying UIO isn't potentially useful,
nor am I saying that it won't potentially give us support for a bunch
of new hardware.  All I'm trying to say is that, to me at least, it is
trying to buy us those new drivers in a way that encourages creating
those drivers as closed source software- *that* is all I'm having
issues with - that is what I think is a step backwards - something
that may give us a short-term gain but will make us lose out
long-term.

> And also realize that some types of systems have been doing this very
> same kind of kernel/userspace interface for many years, namely X :)
>
That something has been going on for years doesn't in itself make it a
good argument for that model.  ;-)

> As for the legalities of using closed source userspace code with the UIO
> interface, consult a lawyer if you have questions, and be sure to bring
> up Alan's comments about derivative works :)
>
I'm not arguing against closed source applications in userspace. That
is of course OK. What I'm arguing about is a kernel interface that
encourages closed source (userspace) *drivers*.

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
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/