linux-kernel - Re: [PATCH 3/3] EDAC: amd64_edac: decide if driver can load successfully early.

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, 19 Mar 2015 10:40:54 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Doug Thompson <dougthompson@...ssion.com>,
	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org,
	linux-edac@...r.kernel.org,
	Mauro Carvalho Chehab <mchehab@....samsung.com>,
	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
	Olof Johansson <olof@...om.net>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Luis R . Rodriguez" <mcgrof@...e.com>
Subject: Re: [PATCH 3/3] EDAC: amd64_edac: decide if driver can load
 successfully early.

On Wed, Mar 18, 2015 at 05:49:10PM -0700, Dmitry Torokhov wrote:
> This change moves setting up PCI control that used to be done after
> driver tried to bind to present PCI devices into the probe() method,
> thus allowing probing to be done asynchronously, if needed.
> 
> To keep as close as possible to the previous behavior we explicitly
> check for presence of supported PCI devices; still we may end up with
> driver loaded even if we did not bind to any of them (for example if ECC
> is disabled).

This is why I did the drv_instances hack - I don't want it to load if
there's no ECC support on the system as it is confusing to people and
tools.

It'd need to be able for the async probing to unload the driver if not a
single node instance loads successfully.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/