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]

Message-ID: <4717CBEC.4060403@rtr.ca>
Date:	Thu, 18 Oct 2007 17:11:08 -0400
From:	Mark Lord <lkml@....ca>
To:	Kristen Carlson Accardi <kristen.c.accardi@...el.com>
Cc:	Theodore Tso <tytso@....edu>,
	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

Kristen Carlson Accardi wrote:
> On Thu, 18 Oct 2007 13:49:25 -0400
> Theodore Tso <tytso@....edu> wrote:
> 
>> 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.
>
> And the answer is most definitely yes to at least a) and c) on specific
> hardware I know about.

I'm hearing a lot of FUD here, with no details.
Please, tell us more..

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