Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp6533222rdb; Tue, 2 Jan 2024 05:19:04 -0800 (PST) X-Google-Smtp-Source: AGHT+IEOix+UMxbvMBKqHDkOO8MbkXaWsafKJVPkmo2Q1vvGznL3rVUAsCmNh5hKUOvESYOqjpHW X-Received: by 2002:a05:6e02:2220:b0:35f:e26e:979a with SMTP id j32-20020a056e02222000b0035fe26e979amr27834218ilf.38.1704201544261; Tue, 02 Jan 2024 05:19:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704201544; cv=none; d=google.com; s=arc-20160816; b=RxweDq5hG3qUpqI0pKP3wGVaY2jUTBYIClgInXLVgG976p+d9UdkiYlV3IX4EtGYlw 82r/efRJ06cfkyP00yuY0s1tKXQRAUQiuMqd45R/PxwA16uKrYCbqXoQpRSf+1hmla91 D2m9xPl/TzspKY7pMMDCcqJ2m0svdrrn6f1DzPgisJXgaD+mHiynhYmrIBY1cxa51KvT PO6Bjr5py3IVkmJcgEEQuw/srVaj22PxaWDgAy4LxXkS6vGGuezHTYkHdE10UWLT88h6 X1hw149a0Wr9QMRYgJt2RHFZB2o+cy1OKtRu5p5r6dkOWYAtRYpxMuVvK1eeAXR8rq8h mCug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:list-unsubscribe:list-subscribe :list-id:precedence; bh=1Z/aZekOHHjZPa6W+lRfUU70kAOn6yYoCT3d0V22B6s=; fh=fnH9hi1aqVH9h6AWKrpExYLQGHLYX9MeKbUGpiTn0cM=; b=jTEfb7Mg//P3nr06MuJ8SsLEnRiwwOAKgmeNGPnU53sOHg90uiiqMOvk/DdzphJ+6s y8NS/Cone7mMaHnn6h8eLW+aWU4OXjKPimqMu83ADJLycz72xZx7wFFu/a8hSsD9JQgg AoOHxi4jUYlUUC9i47pNfMEPprLByPx2GSHCiePhfUW7wh2dDPQ7+GskMtKEMf2QhD0C r3joZkPjNmQFY2LIeKFTby5Oomw1hnxJAkHprCQ52uIx05ek16zV0VxVDgtIh4kaqjlj yUvyhiy9CQB2EHT0fhEz0UIrJGivKM3NhLVTAW5ek7jBecXlUwxN3ZPcq/seV/YksMGD a54A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel+bounces-14395-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-14395-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id p63-20020a634242000000b005cdf4899a56si18085161pga.658.2024.01.02.05.19.03 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 Jan 2024 05:19:04 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-14395-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel+bounces-14395-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-14395-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id DE9D8281295 for ; Tue, 2 Jan 2024 13:19:03 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 0F781FBE5; Tue, 2 Jan 2024 13:18:57 +0000 (UTC) X-Original-To: linux-kernel@vger.kernel.org Received: from mail-oo1-f51.google.com (mail-oo1-f51.google.com [209.85.161.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5AD68F9E6; Tue, 2 Jan 2024 13:18:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-oo1-f51.google.com with SMTP id 006d021491bc7-5958d3f2d8aso270136eaf.1; Tue, 02 Jan 2024 05:18:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704201534; x=1704806334; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1Z/aZekOHHjZPa6W+lRfUU70kAOn6yYoCT3d0V22B6s=; b=LnngeC/Ulg5L8H12/YVUsUM/qOxGeuv04apZmdLzImzt9MtQUU2UKon/ns3tKqMONF pjnxR9XybHo4wA8dXGJefzCWkzWDAg46lyLk+E0yX8qrxH5V+X2lnHv2gBLWP3PIEh9T loLamdecVU9lgQgu5graglljSmKOOLX8tySH0WzkHGWYKRZZikjMO6ZD/VBNsb8OhtGz v60euh1XItjkpoJP+a5HGPkCv60V4lwtD13U68q3SkWkXoebbxsGNUUxZpoHh9Wt/XZo O49VBuTiEIwKv98g0c4GCJiyf/A5U5P3m4dGHbQS54VavCVMBWvKNKndgxkKmOKUK/l/ wxRQ== X-Gm-Message-State: AOJu0YwWtECialLn6dzKAvP0Oo1DZckezqqVMPW87t5W5PByA22ks0Z/ DyzPf7qpHbQkZXuPurDvt/+ppB7ARDG8i/H+wAGo4YVs X-Received: by 2002:a4a:da55:0:b0:595:e0dd:9f8a with SMTP id f21-20020a4ada55000000b00595e0dd9f8amr1053638oou.1.1704201534446; Tue, 02 Jan 2024 05:18:54 -0800 (PST) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <2023122701-mortify-deed-4e66@gregkh> <5754861.DvuYhMxLoT@kreacher> <6019796.lOV4Wx5bFT@kreacher> In-Reply-To: <6019796.lOV4Wx5bFT@kreacher> From: "Rafael J. Wysocki" Date: Tue, 2 Jan 2024 14:18:43 +0100 Message-ID: Subject: Re: [PATCH v1 0/3] PM: sleep: Fix possible device suspend-resume deadlocks To: "Rafael J. Wysocki" Cc: Greg KH , linux-pm@vger.kernel.org, Youngmin Nam , rafael@kernel.org, linux-kernel@vger.kernel.org, d7271.choe@samsung.com, janghyuck.kim@samsung.com, hyesoo.yu@samsung.com, Alan Stern , Ulf Hansson Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Dec 27, 2023 at 9:41=E2=80=AFPM Rafael J. Wysocki wrote: > > 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]). Given the lack of negative feedback, I've queued up this series for 6.8-rc1= . Please let me know if there are any issues with that. Thanks!