linux-kernel - Re: [PATCH 0/3] ipmi: Cleanups for allowing IPMI support to always be "y"

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: <3293311.NLXg2udD5E@vostro.rjw.lan>
Date:	Mon, 24 Feb 2014 13:43:14 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	minyard@....org
Cc:	OpenIPMI Developers <openipmi-developer@...ts.sourceforge.net>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Russ Anderson <rja@....com>,
	Matthew Garrett <matthew.garrett@...ula.com>, lenb@...nel.org,
	linux-acpi@...r.kernel.org
Subject: Re: [PATCH 0/3] ipmi: Cleanups for allowing IPMI support to always be "y"

On Sunday, February 23, 2014 08:23:33 PM minyard@....org wrote:
> Three patches to remove issues with probing interface default, to make
> sure the driver is completely idle if nothing is happening on it, and to
> compile the IPMI driver into the kernel if ACPI is enabled.
> 
> The ACPI spec really requires that the IPMI driver be built into the
> kernel because ACPI uses IPMI for some operations.  But some people
> do not want the driver even using the mimimal amount of CPU it uses
> when idle.  And the default probing, even though sort of implied to
> be required by the spec, is really a bad idea and can result in hangs
> on systems with other hardware at those location.
> 
> Hopefully these patches make everyone happy.

No objections from my side.

I'll drop the Matthew's patch ([3/3] in this series) from my tree, then, so
please carry it along will any followups if needed.

Thanks,
Rafael

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