linux-kernel - Re: Industrial device driver uio/uio

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]

Date:	Thu, 5 Oct 2006 17:12:47 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andrew Morton <akpm@...l.org>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>
Subject: Re: Industrial device driver uio/uio_*

On Wed, Oct 04, 2006 at 09:32:25PM +0200, Thomas Gleixner wrote:
> On Wed, 2006-10-04 at 12:18 -0700, Andrew Morton wrote:
> > On Wed, 04 Oct 2006 19:59:54 +0100
> > > I would just NAK it but want to be sure the guys saw the list of
> > > problems
> > > 
> > 
> > cc's added.
> > 
> > Thomas has been a bit tied up with timers and interrupts of late.
> 
> Yup. fork(tglx) still returns -ETOOMANYINSTANCES.
> 
> I have no objections, if you pull it from -mm for now. The list of flaws
> is accepted and we'll work on this in foreseeable time, _IF_ there is
> some basic consensus about the idea itself not being fundamentaly wrong.
> 
I've got a few cycles I can throw at this, it's a problem space we
(Renesas) are interested in too..

Alan, is your Sept. 11 list the extent of your issues with the current
code, or was there more that you sent off-list?

I'll toss up a quick git tree for this so we don't lose anything, and
the fixes can trickle in to -mm that way, or it can just be pulled and
added back later.
-
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/