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: <20090622151515.GA16627@pengutronix.de>
Date:	Mon, 22 Jun 2009 17:15:15 +0200
From:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, linux-rt@...gutronix.de,
	Thomas Gleixner <tglx@...utronix.de>,
	Ian Abbott <abbotti@....co.uk>,
	Frank Mori Hess <fmhess@...rs.sourceforge.net>
Subject: Re: [PATCH -rt] disable building all staging drivers

Hi Greg,

On Mon, Jun 15, 2009 at 01:00:44AM +0200, Uwe Kleine-König wrote:
> On Sun, Jun 14, 2009 at 04:28:02AM -0700, Greg KH wrote:
> > On Sat, Jun 13, 2009 at 11:38:38PM +0200, Uwe Kleine-König wrote:
> > > I know that at least COMEDI and RT2870 are broken with -rt,
> > 
> > I didn't know this, has anyone sent me a bug report?  What in -rt causes
> > these drivers to break?
> > 
> > > but Thomas requested disabling all of staging.  He's the maintainer.
> > 
> > This seems like a patch to ensure that the staging drivers never get a
> > chance to be fixed for any potential -rt issues.  How about just sending
> > me bug reports instead?
> I cannot reproduce the failure I saw for RT2870 at the moment.
OK, hit again:

17:02:43 E: ERROR: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/staging/rt2870/rt2870sta.ko] undefined!

Best regards
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ