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: Wed, 19 Jun 2024 20:33:11 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Mario Limonciello <mario.limonciello@....com>, linux-pci@...r.kernel.org,
 linux-usb@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Mathias Nyman <mathias.nyman@...el.com>
Cc: LKML <linux-kernel@...r.kernel.org>, Daniel Drake <drake@...lessos.org>,
 Gary Li <Gary.Li@....com>, Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: [PATCH 1/4] PCI: Check PCI_PM_CTRL in pci_dev_wait()

> A device that has gone through a reset may return a value in PCI_COMMAND
> but that doesn't mean it's finished transitioning to D0.  On devices that
> support power management explicitly check PCI_PM_CTRL to ensure the
> transition happened.  Devicees that don't support power management will

                        Devices?


> continue to use PCI_COMMAND.

Would the tag “Fixes” be relevant for such a change description?

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ