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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 19 Mar 2015 16:59:53 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Tejun Heo <tj@...nel.org>,
	Doug Thompson <dougthompson@...ssion.com>,
	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 Thu, Mar 19, 2015 at 08:52:53AM -0700, Dmitry Torokhov wrote:
> Why does the number of bridges matter? Yo can have bazillion bridges, it

Because it only makes sense to leave the driver loaded when at least one
northbridge supports and has ECC enabled.

> doe snot mean you'll have more than one copy of driver code. Note that
> even with the changes we do not leave the driver bound to the devices if
> there is no ECC.

I know, but the driver remains loaded and it could mislead people that
they actually have error decoding enabled.

Btw, why are you guys jumping on this driver?

I don't really believe it would matter if it loaded asynchronously on
the type of boxes it is supposed to be running. So why not mark it as
sync and we all forget about the whole issue?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ