linux-kernel - Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

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, 16 Jun 2016 16:56:57 +0200
From:	"Rafael J. Wysocki" <rafael@...nel.org>
To:	Peter Jones <pjones@...hat.com>
Cc:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Mario Limonciello <Mario_Limonciello@...l.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Len Brown <lenb@...nel.org>,
	"Rafael J . Wysocki" <rjw@...ysocki.net>,
	Andy Lutomirski <luto@...capital.net>
Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of
 PCIe hotplug.

On Thu, Jun 16, 2016 at 2:12 AM, Rafael J. Wysocki <rafael@...nel.org> wrote:
> On Thu, Jun 16, 2016 at 12:15 AM, Peter Jones <pjones@...hat.com> wrote:
>> Right now when booting, on many laptops the firmware manages the PCIe
>> bus.  As a result, when we call the _OSC ACPI method, it returns an
>> error code.  Unfortunately the errors are not very articulate.
>
> What exactly do you mean here?
>
>>  As a result, we show:
>>
>> ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
>> acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
>> \_SB_.PCI0 (33DB4D5B-1FF7-401C-9657-7441C03DD766): _OSC invalid UUID
>> _OSC request data: 1 1f 0
>
> So _OSC told us that the UUID was invalid, didn't it?

BTW, the above messages are KERN_DEBUG, so at least in theory they
shouldn't be visible in production runs.

Maybe the bug to fix is that they show up when they aren't supposed to?