Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3667794imm; Mon, 30 Jul 2018 01:01:03 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcHx3sxL+OZVR3/iXsCPz0eR9WqPVn3txgu4r4fP+FC5CJG4ZgiBIJQIUfLk2W0F4Lb07Gp X-Received: by 2002:a63:68c1:: with SMTP id d184-v6mr15447431pgc.239.1532937663242; Mon, 30 Jul 2018 01:01:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532937663; cv=none; d=google.com; s=arc-20160816; b=rHioV8YMgdDMKmqsqRw6zw15I4Aiwf150ib4Ya+KVH86hVPpbpX8x2b4ghyAJlZG2y skOBkLq42RcUeiU0UZdBW82+69KPC7c8XZsN0NNxAcFdojqZZrSYtMB3h783wBr0Tyjc hnD4Y/XFxwDruubME2u7ZigpkbMsQErFJQtyTRtL3m/pRVeKi17f0MmM6hSunAHU+mY9 x6XWvlr5jezJMVpjt8rOa4up2WpHK7/zc4tdPLicHCO+ImxRP8XI8JdcP9y9ArsnKqMv Dq2PCVlIf7SlVBfflGg/ebSH/fJl29/DbAWe+s4XzW1zn1ICj5JJECu9kLAOrR2nJh5Z xSFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature:dkim-signature:arc-authentication-results; bh=G51edHxvjsCfSdersHPYPe1W7FvLuaKvW7FK0VltXS8=; b=q9kzw+Pl0uuVcqu0eDhaElBL63GwgqAVaRtWPbfQm/09r9zEK0JgSkDJWor21zxhVf tZl5YOZDD77ErjEQI3kn0C4S/8r/6To3LBQzmfcOF+HTLAEqlLj9kkAqDLX5radfmlzH D1x7SvtYcne8O/xE6wx78PPVtugpPmGC4Jlnzeb18Yeogwh9nDhQhR3A68Vhz+Tb2rcK nGgKM393ur7OCyzBWVjfph+F4CGkt9iyBxGDLeQorZfE1w3Hf11uGvlxSrm5bHJKCGAD FFqRdZ9sCmxDPqAqZ2gDo8TwOuo7tCMUoeppj8aK8vMquAsUQS5g5xcD4i+j3JrF2gKd flxA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@pks.im header.s=fm1 header.b=drV62tJG; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=eG3ZZISR; 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 b4-v6si10564872pgg.537.2018.07.30.01.00.48; Mon, 30 Jul 2018 01:01:03 -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; dkim=pass header.i=@pks.im header.s=fm1 header.b=drV62tJG; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=eG3ZZISR; 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 S1726651AbeG3Jdl (ORCPT + 99 others); Mon, 30 Jul 2018 05:33:41 -0400 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]:37691 "EHLO wout3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726401AbeG3Jdk (ORCPT ); Mon, 30 Jul 2018 05:33:40 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id A43F7358; Mon, 30 Jul 2018 03:59:53 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 30 Jul 2018 03:59:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pks.im; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=G51edHxvjsCfSdersHPYPe1W7FvLuaKvW7FK0VltXS8=; b=drV62tJG n3cALeUwYoQt5rlU8+fu4uALK0+KDOX+xpIqzMQHzdjtezMYQqbZC5vuGnRgmcZE o0uNhFAAMrgwP7AhjUVYWQO4XP1A8fxSsGNW6BBjGbRDSxL4/3ZyYouBzg4v7o4I rDQk6bPUWU/iISGcdZEubZvnLq70/Dqg5mdCurmxHeT8AY8CUQnd6VnHCpNjgozY Sei3BSFyFUF0YdzJtr2jynPIR5JwEBXHHGjUO4ZppCPEjjwZ+i9G/711sxuiEyJS 4GY1dVhGsD/uFts3YrgP1JOV8ybnMWh4eJF5L7poJZeW6MJg/UcoD2KURvPG0Lsp BCLgfLhOtbJSDA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=G51edHxvjsCfSdersHPYPe1W7FvLu aKvW7FK0VltXS8=; b=eG3ZZISRex26P3yLpV4YuxUH6RlmM7eQa6v83t1wftH8/ KsduUPmVo/7giw2YsgEyLXKWBCQDyhPkNWD4VWLxNitOR3sGrYXbLigd1Aci/lAC sD70swJiF8lCU6YwphBEIVKdZcfU7NPefcc66HcV8gfy9y1I7gDQ9nPRHhE603dI LB/EVoTXn+NYpIzaL85R7L/bYfOfwe4sZ9EhmTsQDlR5E9pdtEfcr76W3hUVFTQP yUqS+xmQ6+6pEWuKgGiypW+TgjAiTERDBqRq5knT5Y+JDeZpzcNJIkLoI9hXfVh0 gY5XdCaQcDFJiUr3aig3Hlamz4GCNBRrO1YAKMiyQ== X-ME-Proxy: X-ME-Sender: Received: from apu2.pks.im (x4e30b842.dyn.telefonica.de [78.48.184.66]) by mail.messagingengine.com (Postfix) with ESMTPA id DF019E4014; Mon, 30 Jul 2018 03:59:51 -0400 (EDT) Received: from localhost (10.192.0.12 [10.192.0.12]) by apu2.pks.im (OpenSMTPD) with ESMTPSA id 6304f3c9 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Mon, 30 Jul 2018 07:59:50 +0000 (UTC) Date: Mon, 30 Jul 2018 09:59:49 +0200 From: Patrick Steinhardt To: Tomas Janousek Cc: Ming Lei , Jens Axboe , linux-block , Linux Kernel Mailing List Subject: Re: [PATCH] block: fix NPE when resuming SCSI devices using blk-mq Message-ID: <20180730075949.GA1755@xps.pks.im> References: <20180729094131.4kwuukzgfgtisgya@notes.lisk.in> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <20180729094131.4kwuukzgfgtisgya@notes.lisk.in> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 29, 2018 at 11:41:31AM +0200, Tomas Janousek wrote: > Hi, >=20 > On Fri, Jul 13, 2018 at 09:41:41PM +0800, Ming Lei wrote: > > Now runtime PM is disabled for blk-mq/scsi_mq, not sure how this issue = is > > triggered on your machine. >=20 > While Patrick did miss the following patch: >=20 > * 765e40b675a9 ("block: disable runtime-pm for blk-mq"; July 2017). >=20 > there is at least one other way to trigger it -- enable laptop-mode-tools > or tlp which enable runtime-pm for all devices. >=20 > The "disable runtime-pm for blk-mq" only disables it _by_default_, but do= esn't > prevent it from being enabled again from user-space, which it is unless o= ne > manually blacklists sd devices from runtime-pm enablement. It's bitten a = few > people already: https://github.com/rickysarraf/laptop-mode-tools/issues/1= 23 >=20 > (I found this thread because I'm also getting the NULL pointer dereferenc= e at > 00000000000001a8 on resume from suspend.) Huh, I did send out some more details on how I reproduce the issue, but it seems like my mail didn't get through. While I don't use laptop-mode-tools, I do have some custom hotplugging scripts which do in fact enable runtime-PM for most devices. Regards Patrick --5vNYLRcllDrimb99 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEtmscHsieVjl9VyNUEXxntp6r8SwFAltexXUACgkQEXxntp6r 8SyzOg//T0tHxr7/QEE+jM9OHI6NouFFHh7CubJtlZk9Ocv0VQv/4AY9zSfkkqQ/ 9gkGaRnSbM7J7IMdAMsjDkDB+5FUw7uKIFB+0zCxjUK09Zq9jnhw0yiWMCiwOedh v96KLiacbIa/l6E+h+xMStNv0goGQcF3AzHlDKjgtstJSnL7aD7XX4URve4YeSuQ AAq3yQUbk8tPZcnlJm9SwTXUd6MOoYjCsdl6ptPl7Z1iNrf3ZhGoUzPUaUoG3RE3 4ZqM74Y3KOHTBhXzyZkoz/SFkUghHJGdaZMm7zk8ApfhQAGw0573JPsH4pj4z7h6 b0ad2PYmLn8O2c22w6THQMyVO1HaUQg6ngJfTzZHSaGlwqxNFfAKcwYBbAFUS+fQ Wb6YlIopC2MVYyAK21r+0p50SntCULRu04ptRFe0gILpfc0JnY89DYOPwk7yEClB OXyUKbRXCm/+USe9kKx4vFRzJVdL5Ubohu6v7da6Lm8C6YqZC/o9fYYegrzZdIKB TAZQWhRiscXPqdD2lZtmTpKFp2QuKcbWwi7PSrP4jz2gar/s8xN7LATQThSPOEkK x+uuGQWFaqGQTHDwn7ViRCXX2rtTysu0Q6fztZ3wc75T7fIzkk98XfAPGGbG5pFV qOUKuC7MJaGMOc9g3LJSXblqZUgW/liSvGB7aSecWXVAV2LLACI= =RrcF -----END PGP SIGNATURE----- --5vNYLRcllDrimb99--