Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp695205ybp; Fri, 4 Oct 2019 03:32:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqxLGg8B2P6TbQ0zNECMbeNYjGCn37S1sGFyYziMB/T2AOFqUT99BFZ4mqNWLctHZOUE8iLD X-Received: by 2002:a50:9625:: with SMTP id y34mr14152789eda.72.1570185166030; Fri, 04 Oct 2019 03:32:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570185166; cv=none; d=google.com; s=arc-20160816; b=jYWlcOnURDo8TouhV2hizhDgfvh1WtIvG57rVJO1gpm2Do55zoz7SGj/gcLYtmOwGQ cMmfVntBLLlrTU9PbWqYOtpME5WudcBTrU37qrQNtwtg8KCOYIQU+hraPa5dIY3OO0ny js+HEemNCWZv5cccpUJ15Xk9WjGKBEXuMUJ8EDUEj/FybDzS3cFDaxBx+Ai2bHB7/OcV HurXDKexPVEQQPSJUaatQQLspGJX4fiNilLL0CTjMfz782rIjhBSghu68tBbomNRc+63 imlW3kc+Rtv9/7affVarPO8PUXP7EDIYIy+DAajns0vaAcGdZmIXpfcymeKaSAUoi3RU fGWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=BoenLfpblehlx+zm2U5O1vmoIvm0sypYEufe2vmH7Z4=; b=wRq7xPEZdX4jMOdfomferBkmz0avA36TvIyLWb3+f+J7BBUhdquQQVmJzGdtBq8ZKo 1oCSKHBZna7alb3aZ5n6R5Sw747UOqDw1GI16Y6iHsJP6qqSFipNaZlxk2ueLYINNeXm /sEEpJjbpRaU36e30CINHe2NPHC6bZpPbd/owNXIq2HyrM1vbsWgWbyNhWjUaQ3VDDtD smw3lsLjsaCFhLdbeqBGTo6uZwrTXcAKYNWt2G3K0tUmJVsGjP0/ZlJ7ivaYqIGJ/KD2 dFm+nZXBGDTyeOlS6FzEaMZmZAWsI77IGWir/bhaWe/VUwUjMsNHBzyhL2jE97H2OSEG EzAw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b1si3285998edm.271.2019.10.04.03.32.22; Fri, 04 Oct 2019 03:32:46 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730011AbfJDJ73 (ORCPT + 99 others); Fri, 4 Oct 2019 05:59:29 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:59890 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726393AbfJDJ73 (ORCPT ); Fri, 4 Oct 2019 05:59:29 -0400 Received: from 79.184.253.225.ipv4.supernova.orange.pl (79.184.253.225) (HELO kreacher.localnet) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83.292) id d2f42940dd6adecb; Fri, 4 Oct 2019 11:59:26 +0200 From: "Rafael J. Wysocki" To: Mika Westerberg Cc: Tejun Heo , "Rafael J. Wysocki" , AceLan Kao , Jens Axboe , Jan Kara , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Subject: Re: System hangs if NVMe/SSD is removed during suspend Date: Fri, 04 Oct 2019 11:59:26 +0200 Message-ID: <2367934.HCQFgJ56tP@kreacher> In-Reply-To: <20191004080340.GB2819@lahna.fi.intel.com> References: <20191002122136.GD2819@lahna.fi.intel.com> <20191003165033.GC3247445@devbig004.ftw2.facebook.com> <20191004080340.GB2819@lahna.fi.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday, October 4, 2019 10:03:40 AM CEST Mika Westerberg wrote: > On Thu, Oct 03, 2019 at 09:50:33AM -0700, Tejun Heo wrote: > > Hello, Mika. > > > > On Wed, Oct 02, 2019 at 03:21:36PM +0300, Mika Westerberg wrote: > > > but from that discussion I don't see more generic solution to be > > > implemented. > > > > > > Any ideas we should fix this properly? > > > > Yeah, the only fix I can think of is not using freezable wq. It's > > just not a good idea and not all that difficult to avoid using. > > OK, thanks. > > In that case I will just make a patch that removes WQ_FREEZABLE from > bdi_wq and see what people think about it :) I guess that depends on why WQ_FREEZABLE was added to it in the first place. :-) The reason might be to avoid writes to persistent storage after creating an image during hibernation, since wqs remain frozen throughout the entire hibernation including the image saving phase. Arguably, making the wq freezable is kind of a sledgehammer approach to that particular issue, but in principle it may prevent data corruption from occurring, so be careful there.