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
| ||
|
Message-ID: <6019796.lOV4Wx5bFT@kreacher> Date: Wed, 27 Dec 2023 21:35:53 +0100 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Greg KH <gregkh@...uxfoundation.org>, linux-pm@...r.kernel.org Cc: Youngmin Nam <youngmin.nam@...sung.com>, rafael@...nel.org, linux-kernel@...r.kernel.org, d7271.choe@...sung.com, janghyuck.kim@...sung.com, hyesoo.yu@...sung.com, Alan Stern <stern@...land.harvard.edu>, Ulf Hansson <ulf.hansson@...aro.org> Subject: [PATCH v1 0/3] PM: sleep: Fix possible device suspend-resume deadlocks Hi Everyone, As reported here https://lore.kernel.org/linux-pm/ZYvjiqX6EsL15moe@perf/ the device suspend-resume code running during system-wide PM transitions deadlock on low memory, because it attempts to acquire a mutex that's already held by it in those cases. This series addresses the issue by changing the resume code behavior to directly run the device PM functions synchronously if they cannot be scheduled for asynchronous executions (patch [3/3]). For this purpose, the async code is rearranged (patch [1/3]) and a new variant of async_schedule_dev() is introduced (patch [2/3]). Thanks!
Powered by blists - more mailing lists