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:	Tue, 14 Sep 2010 07:16:12 +0200
From:	Shérab <Sebastien.Hinderer@...-lyon.org>
To:	Valdis.Kletnieks@...edu
Cc:	Samuel Thibault <Samuel.Thibault@...-lyon.org>,
	"H. Peter Anvin" <hpa@...or.com>, Len Brown <lenb@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Andres Salomon <dilinger@...ued.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: EuroBraille/Iris power off

Hi,

Valdis.Kletnieks@...edu (2010/09/13 21:45 -0400):
> I'm agreeing that if iris_init() checks that the user passed 'irisinit.force=1'
> on the command line or as a module parameter, and bailed immediately if it
> wasn't passed, then doing the inb() and testing it should be safe enough. Doing
> stuff that's only known safe on an Iris is no great sin if the user has said
> "Yes, you're on a Iris" - at that point it's the user's fault.

Fine. I'd be happy to submit another patch where the module takes a
force argument if that's okay to you guys.

Shérab.
--
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