linux-kernel - Re: [PATCH] PCI PM: Fix handling of devices without PM support by pci_target

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] [day] [month] [year] [list]

Message-ID: <20090616121828.2a7a8677@jbarnes-g45>
Date:	Tue, 16 Jun 2009 12:18:28 -0700
From:	Jesse Barnes <jesse.barnes@...el.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux PCI <linux-pci@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andreas Mohr <andim2@...rs.sourceforge.net>,
	pm list <linux-pm@...ts.linux-foundation.org>
Subject: Re: [PATCH] PCI PM: Fix handling of devices without PM support by
 pci_target_state()

On Sun, 14 Jun 2009 21:25:02 +0200
"Rafael J. Wysocki" <rjw@...k.pl> wrote:

> From: Rafael J. Wysocki <rjw@...k.pl>
> 
> If a PCI device is not power-manageable either by the platform, or
> with the help of the native PCI PM interface, pci_target_state() will
> return either PCI_D3hot, or PCI_POWER_ERROR for it, depending on
> whether or not the device is configured to wake up the system.  Alas,
> none of these return values is correct, because each of them causes
> pci_prepare_to_sleep() to return error code, although it should
> complete successfully in such a case.
> 
> Fix this problem by making pci_target_state() always return PCI_D0
> for devices that cannot be power managed.
> 
> Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
> ---
> Hi Jesse,
> 
> I think this is 2.6.31 material, probably -stable too.

Applied to my linux-next branch, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/