linux-kernel - Re: [PATCH 0/3] Fix two PEIe hotplug issues

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, 18 Oct 2007 13:49:25 -0400
From:	Theodore Tso <tytso@....edu>
To:	Kristen Carlson Accardi <kristen.c.accardi@...el.com>
Cc:	Mark Lord <lkml@....ca>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>, greg@...ah.com,
	pcihpd-discuss@...ts.sourceforge.net
Subject: Re: [PATCH 0/3] Fix two PEIe hotplug issues

On Thu, Oct 18, 2007 at 10:06:14AM -0700, Kristen Carlson Accardi wrote:
> No, it actually does violate the spec.  Feel free to read it yourself.
> We are not supposed to do Native PCIe without first successfully executing
> OSC.  Period.  If you do, you are violating the spec.

To be fair, we have violated the spec before in order to get crappy
hardware or to work around crappy ACPI implementations.
acpi_sleep=s3_bios for example violates the spec, but yet it is the
only way to get certain laptops to suspend/resume correctly.  

The question to ask is whether violating the spec will lead to (a) a
potential system hang/crash, (b) data corruption, (c) physical harm to
the device/laptop.

Regards,

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