linux-kernel - Re: [PATCH] PCI: Add disabling pm async quirk for JMicron chips

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]

Date:	Mon, 11 May 2015 14:58:58 +0800
From:	Aaron Lu <aaron.lu@...el.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Chuansheng Liu <chuansheng.liu@...el.com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	mister.freeman@...oste.net, Tejun Heo <tj@...nel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	linux-pci@...r.kernel.org,
	Linux-pm mailing list <linux-pm@...r.kernel.org>,
	stable@...r.kernel.org
Subject: Re: [PATCH] PCI: Add disabling pm async quirk for JMicron chips

On Sat, Jan 10, 2015 at 1:46 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> On Fri, Dec 05, 2014 at 02:18:40PM -0500, Alan Stern wrote:
>> On Fri, 5 Dec 2014, Chuansheng Liu wrote:
>>
>> You know, this is exactly why device_pm_wait_for_dev() exists -- so
>> that asynchronous power-management operations can wait for other
>> devices even when there's no parent-child relation.
>>
>> You should try to use device_pm_wait_for_dev() instead of disabling
>> async suspend/resume.
>
> Dropping this patch for now, waiting for a response to Alan's suggestion.

>From Alan's comments #106:
https://bugzilla.kernel.org/show_bug.cgi?id=81551#c106

It seems Chuansheng's patch is the best solution for now, so perhaps
it can be considered to be merged?

Regards,
Aaron
--
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/