Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp583786ybp; Fri, 4 Oct 2019 01:28:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqx4kxUwnznUaNdVUMmszpPkkdkt7yuUnHIUmQYGw/6cvvou7Unu4HCE0SjICFaIjBGFb2sk X-Received: by 2002:a17:906:4b41:: with SMTP id j1mr11171041ejv.162.1570177736641; Fri, 04 Oct 2019 01:28:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570177736; cv=none; d=google.com; s=arc-20160816; b=HvDlw3ccFfbPX77b+kBp9As3TZJxOUBRMBTK6pHzjTMOyCsMUnuHm7ioqyQCdAhD5M L1ulLLXS0xTZpr3YKsTz+i3TMD5bwhTfpgWge0AojyCwV2XyQ8thpN2/9iDInpj5sbIQ I78VKlwHEhd/fTZIMTL+/uhLBUwaOe1Z65B9s68axwNbgS1bedatf2dwQcjLMj3Upe9T VehOA71TN7ZyK2cxEn9zNfjZX15piGB2Z63QW7ajmltwPDsL8Wld4AZmVI3xPS+2n2qA tR5t+V1WIb9qzV9jwi1jENsYkoGQGCr7uu9y8Koe/6yRd0YF4SV2h1/sPnawzk/zo6DJ yG2Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=JAg0JDhZCg4id3tnc80iKIY/Iykn51Zai2heE6tc0kM=; b=NptborcZ0tCm6KZSnlH5q9l2LmfoYVJVB3+0sopwA3C+aQLKTxBVVL/CqNaywZ6wme anvRsJgFHjnQglZQey+1UE98RnrfoSWKLshL2oakD+S/HBC4xQZ2YiqXiMtBbt3d+oQm knusl/nZIrBr5EGCtg9A8qukq8AIWwf5qu7pAoOlmjb6mT1NesgPE/A9i8W64MiFHZV5 fzAcYdjYWlwDRSsH+sAHczg8yH1qXQiVl/UEur4ZQu2pJSHV3uD6SVkUSWLoS2cQsGBT gbcI8qm4S+m3kzN2b8qYYr4bdT2pDHRC5GjVeM3y2knD8Zw4VyvhsWJCvGXu2hCXGM+n LBQw== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y9si2962455edv.405.2019.10.04.01.28.33; Fri, 04 Oct 2019 01:28:56 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730885AbfJDIDo (ORCPT + 99 others); Fri, 4 Oct 2019 04:03:44 -0400 Received: from mga11.intel.com ([192.55.52.93]:28702 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729252AbfJDIDo (ORCPT ); Fri, 4 Oct 2019 04:03:44 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Oct 2019 01:03:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.67,255,1566889200"; d="scan'208";a="205802407" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.157]) by fmsmga001.fm.intel.com with SMTP; 04 Oct 2019 01:03:40 -0700 Received: by lahna (sSMTP sendmail emulation); Fri, 04 Oct 2019 11:03:40 +0300 Date: Fri, 4 Oct 2019 11:03:40 +0300 From: Mika Westerberg To: Tejun Heo Cc: "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 Message-ID: <20191004080340.GB2819@lahna.fi.intel.com> References: <20191002122136.GD2819@lahna.fi.intel.com> <20191003165033.GC3247445@devbig004.ftw2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191003165033.GC3247445@devbig004.ftw2.facebook.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 :)