From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id EB4613254BB
	for <linux-kernel@vger.kernel.org>; Wed, 27 May 2026 15:46:35 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1779896797; cv=none; b=uVs/NCaTgZJpjVtkaRrF6aazX3RPz7dqDUNzhlZeo1LckVoxIDZ/y0wVtMv519QHUMie2YpM38CtVBvlngavHrcGZt42g/nNC2SZ0iAqRFAB/8LOwv6vfV8l0201Hnl8Jgvyt58N+pFDllIi/Bf8Cr0kuP1cez+uw98s1Lnf/Fw=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1779896797; c=relaxed/simple;
	bh=RSJpJJqFdrJxLEE58UNzbaTpmKMjawEvkKpKdcyr8wA=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=j4IHCo01p5vCnQsQLlK59pase7exA+PXn/Q2vUZNsnR9CG8WiT0IVk+QMn4QoiKR0XYfI+6DdaQs9Kjgvw3veT2LGL3iYZVVK59vyXV2gBxCpnYXS7oVMLAqSXGsgt649YwVDv/uyBL2G5BPXtAuBS6OjT5OhUnDOt9s5k4JbhU=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=H7MSrAo8; arc=none smtp.client-ip=100.103.45.18
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="H7MSrAo8"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 69C531F000E9;
	Wed, 27 May 2026 15:46:35 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org;
	s=k20260515; t=1779896795;
	bh=RSJpJJqFdrJxLEE58UNzbaTpmKMjawEvkKpKdcyr8wA=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To;
	b=H7MSrAo8cnQvLI7EPixVHkikvrIZADmroiUQfYgvY1GI9mdmz/AugHzwUEl9uVrgt
	 l0nL/7tCMaOg9Z+/4s4ccWcQXQ0ZNXHK2zM/pT233kVgaHmZVU53EnAHeazc1xshVK
	 b5c949ARCZf70qKNwXUtrKlL0/bGknMvwWuKMNwp9HtkpjO2KVctFmMLXcMovMOLy5
	 S9I5oEMMZHjYfPnDsDYto0PmynQmQ6VVSR9oht63oYRcz9xgwMdNLEuXDZqcNZz0Xd
	 Z1SD5r/LjXPOoJCimqbWkSHSVlP35GgvodWMDAj2eG0+5jA7gzyrqUrZda89TTnhCT
	 iybmIFNKYt+vg==
Date: Wed, 27 May 2026 09:46:34 -0600
From: Keith Busch <kbusch@kernel.org>
To: Chao Shi <coshi036@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <kch@nvidia.com>, linux-nvme@lists.infradead.org,
	linux-kernel@vger.kernel.org, Sungwoo Kim <iam@sung-woo.kim>,
	Dave Tian <daveti@purdue.edu>, Weidong Zhu <weizhu@fiu.edu>
Subject: Re: [PATCH] nvme: bound the freeze drain in passthrough commands
Message-ID: <ahcR2vy8k2FZAp9D@kbusch-mbp>
References: <20260527055923.456769-1-coshi036@gmail.com>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20260527055923.456769-1-coshi036@gmail.com>

On Wed, May 27, 2026 at 01:59:23AM -0400, Chao Shi wrote:
> If a completion is silently dropped or the device hangs, the calling
> task wedges with ctrl->scan_lock and ctrl->subsys->lock held, fanning
> out into hung-task reports on any concurrent open/close/passthru on
> the same controller:

The IO timeout callbacks that nvme drivers provide are supposed to
forcefully reclaim any IO no matter what state the device is in. Is that
not happening for some reason?