Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp4153982pxb; Mon, 27 Sep 2021 10:29:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz+3R8CcsKbZtqLAfPeBNaU8M+h7jy15SMm0NHKrlbEzf7jHSCJbf6OtyupdIbMAjw36LzM X-Received: by 2002:a63:2a0f:: with SMTP id q15mr691107pgq.205.1632763762238; Mon, 27 Sep 2021 10:29:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632763762; cv=none; d=google.com; s=arc-20160816; b=dDEPmLHDMAeN9XT42Z71MrWehkuuXIphYkBh2ifBp1FqouUjUxlvrFg1PoenR10a6N gMfAlg248CDIwmZU5+lIrFPm1NqghJJ9OAdzY1GST7mwELngbxeYtuEj3wih/Jp0shVe Opke8HCdgxMnP1jpTqMRa9vYFhzupVuHC/+G23cEY6R2glu1CInc5i9Ap5aHLdudIjl/ g2ssgxpOqQ6GX2nsjqgR1Wz+283HrY7QcvOU1AuZMSu+Sec8WYK1WGF2AkgrXcW+Ttq1 TmPFhHTIe/EUEY45Nd6gbY/+arXl9JxT2aVStFj5aCzkR7AMX5NYvGibRC73Xyo3/ZJv Pzyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=K1meAwtK2pPQTJ7EUrLKRCyr5DzSYAIJAQuJDBxqaqY=; b=dmQaNjKYXEkXPOPc6R2kOH5OvCjwLi63K3Gom5cWlyJdqZYJoRHxJN8wUCehHeI5DB AZa7FN7ZTYu775DQEThz5aZPCpBiRaRfmwKpiof9tHu7l2KwwK6Jo2Fwg2bm0vBfgB31 Kfv0aBt6vx64hA2J7+sOy64C8TpbrZsJTifyfTDxnHJquLwhEHyWP/myom2IIdm6XdfM HozmCwzpkiI51sqmFwg1Klfg4RLQYOeEU623iF1FdtIiDXQJy3+3n32qPFBSRHDIPBmN q6L3vppAiSNUqCINmXdy2ic/A6UWmhJxNp8OIkv3VF/N5P5y2h/MZ5DqMy+wF5HVVI02 BeTg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="DQ/yQmKC"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x6si21941336plr.54.2021.09.27.10.29.07; Mon, 27 Sep 2021 10:29:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="DQ/yQmKC"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238025AbhI0RaB (ORCPT + 99 others); Mon, 27 Sep 2021 13:30:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:44586 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235622AbhI0R0s (ORCPT ); Mon, 27 Sep 2021 13:26:48 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id F1A676138E; Mon, 27 Sep 2021 17:16:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1632763006; bh=Z+h5UCQ1pHGq30LcDVJRyF4/ArN7q2q2X4cNJCzUbT8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=DQ/yQmKCsyTW4ExtzdGF09/ahvP9ZPNDo7ieproMTD7m8jjhCwRVxaQ/lFrerMELc SsGmUIPnpluIIWjV8IfjxrOOC1laEqUu1D5n+DLfv19LNEms/ZeHSO6pe/hCGoUFjG hqs2nivqtsoNW1x6RahA5BsqBSkMI0N9CC7f3KDc= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Lihong Kou , Christoph Hellwig , Sagi Grimberg , Jens Axboe , Sasha Levin Subject: [PATCH 5.14 133/162] block: flush the integrity workqueue in blk_integrity_unregister Date: Mon, 27 Sep 2021 19:02:59 +0200 Message-Id: <20210927170238.033503340@linuxfoundation.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20210927170233.453060397@linuxfoundation.org> References: <20210927170233.453060397@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Lihong Kou [ Upstream commit 3df49967f6f1d2121b0c27c381ca1c8386b1dab9 ] When the integrity profile is unregistered there can still be integrity reads queued up which could see a NULL verify_fn as shown by the race window below: CPU0 CPU1 process_one_work nvme_validate_ns bio_integrity_verify_fn nvme_update_ns_info nvme_update_disk_info blk_integrity_unregister ---set queue->integrity as 0 bio_integrity_process --access bi->profile->verify_fn(bi is a pointer of queue->integity) Before calling blk_integrity_unregister in nvme_update_disk_info, we must make sure that there is no work item in the kintegrityd_wq. Just call blk_flush_integrity to flush the work queue so the bug can be resolved. Signed-off-by: Lihong Kou [hch: split up and shortened the changelog] Signed-off-by: Christoph Hellwig Reviewed-by: Sagi Grimberg Link: https://lore.kernel.org/r/20210914070657.87677-3-hch@lst.de Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin --- block/blk-integrity.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/block/blk-integrity.c b/block/blk-integrity.c index e9f943de377a..9e83159f5a52 100644 --- a/block/blk-integrity.c +++ b/block/blk-integrity.c @@ -430,6 +430,9 @@ void blk_integrity_unregister(struct gendisk *disk) if (!bi->profile) return; + + /* ensure all bios are off the integrity workqueue */ + blk_flush_integrity(); blk_queue_flag_clear(QUEUE_FLAG_STABLE_WRITES, disk->queue); memset(bi, 0, sizeof(*bi)); } -- 2.33.0