linux-kernel - Re: [PATCH 6/8] amd64_edac: enforce synchronous probe

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]

Message-ID: <20150319170452.GJ30732@dtor-ws>
Date:	Thu, 19 Mar 2015 10:04:52 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Luis R . Rodriguez" <mcgrof@...e.com>,
	linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Olof Johansson <olof@...om.net>,
	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Subject: Re: [PATCH 6/8] amd64_edac: enforce synchronous probe

On Thu, Mar 19, 2015 at 12:19:27PM -0400, Tejun Heo wrote:
> Hello,
> 
> On Thu, Mar 19, 2015 at 09:01:46AM -0700, Dmitry Torokhov wrote:
> > I think that would be the goal, yes, but I think we'd need some "trial"
> > period before we can do that: I need to look into at least serial and
> > regulators to make it work (not even considering any userspace). We are
> > definitely not ready just yet and that is why I have a whitelist: there
> > are classes of devices that all userspaces learned to deal with long ago
> > and we can make them not stall boot right now.
> 
> Yeah, as I wrote before, as long as there's a plan and push to finish
> the conversion, it's fine.  I'm just worried that this might rot in
> the grey area.  Can we please update the patches so that it's clear
> that the whitelist is a temporary measure both in the description and
> code?

OK, will do.

Thanks.

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