Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp1476074img; Tue, 19 Mar 2019 08:25:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqym2AIZzw+eHzrhEjxhk9kzoE8YsLTg7u9lq9eqDhcgooLqXGjKTlv0jpHYdjYWbWy9iHH5 X-Received: by 2002:a17:902:1102:: with SMTP id d2mr2522198pla.329.1553009146319; Tue, 19 Mar 2019 08:25:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553009146; cv=none; d=google.com; s=arc-20160816; b=ZYHyAwWj6FRHhVAYq3DIkcqWZM1kCUvNgWBjyJyebpCfW9DzjlhhCG1/bWsfjWawCY CosS7KCHS+HxxqOYHLw9W8VXuF2BXyC2QHbgCOlte24VlqY6gvitsP4v6qYBlEAIa8HV gpEFM6B7GhDftFGGr03n2sjC2RJmG/RLUk4CwjpE2n0/5FRzlhZjpQlf/tU98n9YoRrG zr4G4EFNe+3UBLHa9gx4grb8NXPHkSdFHsQ3noaZV6mBfhlfkKsMBqMmpqjXCGt7NN29 dp7IWBrbXt+ulmWN7e04lC/e/+D4u07mzHqwQQLWuP64PBxZJsP6O3h8EIqDaiNkfBvz 45ZQ== 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=Xie/0NF1dRNV8W5MyUzM+hzbUdbqLi1QwRYp3JSrFCo=; b=XbJZOHFIje/8cxsq4BIoTpgdGdzngf3kIK0ucHPBJx2uFvUtBLN1uo3HcZGt4iLhbI 4P5AfvSljhWqFadPU52IXMKDJzLINhW42Yq2sQpGI1qHIA1XR1elObgfJbIhtVvX7izu Awv5EwyzwNZCZF9BltpAbFUbBl7C9WkXLB0uzb7QTjF5gyaTree7rwGS3ZgT1J0PMRNL vCLSRlwatdwePbd2jqHD4XBZ5fjVINg1oW8YNTwUSyeak4uyOp/412ZFMTyP5mWU+kkX VR9Idgvue9NGYRbzxJS0zN5DgwTknyHwKOdF91/8mTLT19ODgQgDAGl/gtbRdWcoPqU7 dzIQ== 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 q16si5453782pgi.446.2019.03.19.08.25.29; Tue, 19 Mar 2019 08:25: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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727611AbfCSPYk (ORCPT + 99 others); Tue, 19 Mar 2019 11:24:40 -0400 Received: from mga01.intel.com ([192.55.52.88]:45109 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726579AbfCSPYk (ORCPT ); Tue, 19 Mar 2019 11:24:40 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Mar 2019 08:24:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,498,1544515200"; d="scan'208";a="135598379" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by fmsmga007.fm.intel.com with ESMTP; 19 Mar 2019 08:24:38 -0700 Date: Tue, 19 Mar 2019 09:25:34 -0600 From: Keith Busch To: Bart Van Assche Cc: "jianchao.wang" , axboe@kernel.dk, linux-block@vger.kernel.org, jsmart2021@gmail.com, sagi@grimberg.me, josef@toxicpanda.com, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, keith.busch@intel.com, hare@suse.de, jthumshirn@suse.de, hch@lst.de Subject: Re: [PATCH 0/8]: blk-mq: use static_rqs to iterate busy tags Message-ID: <20190319152533.GD24176@localhost.localdomain> References: <1552640264-26101-1-git-send-email-jianchao.w.wang@oracle.com> <1552930085.152266.36.camel@acm.org> <3cd58454-eda3-de9a-0eed-b6a7edbce28f@oracle.com> <1553008222.152266.43.camel@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1553008222.152266.43.camel@acm.org> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 19, 2019 at 08:10:22AM -0700, Bart Van Assche wrote: > On Tue, 2019-03-19 at 09:25 +0800, jianchao.wang wrote: > > Do you mean this patch from Jens ? > > https://marc.info/?l=linux-block&m=154534605914798&w=2 > > > > + rcu_read_lock(); > > sbitmap_for_each_set(&bt->sb, bt_iter, &iter_data); > > + rcu_read_unlock(); > > > > The busy_iter_fn could sleep for nvme > > blk_mq_check_expired > > -> blk_mq_rq_timed_out > > -> q->mq_ops->timeout > > nvme_timeout > > -> nvme_dev_disable > > -> mutex_lock dev->shutdown_lock > > Hi Jianchao, > > I think that's an additional reason to rewrite NVMe error handling ... Nonesense. Block timeout handling runs in a work queue precicesly so handlers can actually do useful work in line with the notification.