Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp8049967imu; Tue, 4 Dec 2018 01:59:18 -0800 (PST) X-Google-Smtp-Source: AFSGD/Xj9uzzRsxyYYUfTLFrMDotlmfPixtwPje6dFsdnVNkCezbpACbE+AupKeKn7fKfMCnayag X-Received: by 2002:a63:3858:: with SMTP id h24mr14502976pgn.300.1543917557980; Tue, 04 Dec 2018 01:59:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543917557; cv=none; d=google.com; s=arc-20160816; b=n25jvlnLqhjnowDGmQUAd/H++G7GPPRJWV9MsrNVkVlBw7KDVQYviWbzG8tqRoi5Kf /NVdm3lCkPoX+TyG9BXnTU7Qc8BYED8HqGnx44gvWKmfE5HWBMRAtDWQf+LUaBzudiS9 +zeRKtZM/CJ+ur3myTceBykCcRHh7rMBkHTsEHe8asUUo4sDEojD3aCgM2bbnM5MNtDs BLGHr90Ht411qyS8t6555VV4m8m3eO0y7W1HXh7Vr6P2RiLGtH0R3KQA4wUCV7mWfzEy IyR9ihQXYF+DS2k4gQIlddFsSCsKzXbMvC4dxzNJsS6EKJ9zHKFTtGtPwg4yKKZL+nTV veIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=u+E8mr8qbfnHCtlTash/vErYCHPiA5vcq1TtcILbvbo=; b=wAhzrL054Y1XediRrfqkVgO2gOrDfvEnhBddGBMpSQprF9nJbWW9fOQybOyjmP2vVH GEnZ2sekgDZWq5gNxUVXwsxQzOIzTBO5ZOz5scvUknhvfKid9Yl3KJIoxgYu+NFXo4lH 0fSaS2Czq7BDNI96HhV/9T/8VQ+6owNrRRVchVjWqzpsUOkW5Xe0TER1bJez9yrrs6aA 25PpUrWR2ZP5WNn0JxBPammZJYjBAjVOnTglJJcCQQApw5qlkDTxZ+A3R7t5y+ft49Nl QeCH4O62qsqD3fsjqvPduZg+FulNmy7satYZ2SyfO04eGKWTUgYwEHP7qygVuF5kZ9z5 PgWg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cf16si17646631plb.227.2018.12.04.01.59.02; Tue, 04 Dec 2018 01:59:17 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726132AbeLDJ6J (ORCPT + 99 others); Tue, 4 Dec 2018 04:58:09 -0500 Received: from mx2.suse.de ([195.135.220.15]:33588 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725949AbeLDJ6I (ORCPT ); Tue, 4 Dec 2018 04:58:08 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 50196AC24; Tue, 4 Dec 2018 09:58:05 +0000 (UTC) Date: Tue, 4 Dec 2018 10:58:02 +0100 From: Michal Hocko To: Ingo Molnar Cc: Pavel Machek , Oleg Nesterov , Linus Torvalds , Linux List Kernel Mailing , "Rafael J. Wysocki" , Chanho Min , Thomas Gleixner , Peter Zijlstra Subject: Re: [PATCH] Revert "exec: make de_thread() freezable (was: Re: Linux 4.20-rc4) Message-ID: <20181204095802.GF1286@dhcp22.suse.cz> References: <20181203083942.GF31738@dhcp22.suse.cz> <20181203123149.GB31795@redhat.com> <20181203123857.GS31738@dhcp22.suse.cz> <20181203131006.GA10054@amd> <20181203135351.GU31738@dhcp22.suse.cz> <20181203141459.GA14789@amd> <20181203141737.GY31738@dhcp22.suse.cz> <20181204090228.GC73770@gmail.com> <20181204091020.GD1286@dhcp22.suse.cz> <20181204093310.GE73770@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181204093310.GE73770@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 04-12-18 10:33:10, Ingo Molnar wrote: > > * Michal Hocko wrote: > > > I dunno. I do not use hibernation. I am a heavy user of the suspend > > though. I s2ram all the time. And I have certainly experienced cases > > where suspend has failed and I onlyi found out later when I've picked > > up my laptop from my heat up bag. Nothing fatal has resulted from that > > but this is certainly annoying. > > Hm, so I (mistakenly) thought freezing was mostly limited to hibernation > and to a few weird cases when in flight DMA must not be suspended - but > I'm wrong and in practice we always freeze tasks during s2ram, right? Yup. > And indeed: > > config SUSPEND_FREEZER > bool "Enable freezer for suspend to RAM/standby" \ > if ARCH_WANTS_FREEZER_CONTROL || BROKEN > depends on SUSPEND > default y > > which is essentially always enabled on x86. > > TIL ... > > s2ram is obviously a huge deal. > > Just a newbie question: any chance to not do any freezing at all on > modern laptops when doing s2ram, or at least only warn if it fails and > try to suspend? AFAIU both suspend and hibernation require the system to enter quiescent state with no task potentially interfering with suspended devices. And in this particular case those de-thread-ed threads will certainly not interfere so silencing the lockdep sounds like a reasonable workaround. -- Michal Hocko SUSE Labs