Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3868089pxv; Mon, 19 Jul 2021 10:40:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz7EGFLCv8HUuWVLLe6bBwzWw/D5POEBPCa/e6Hki3LqAt75yR0SfCzsAzqRqHSgsXskbMa X-Received: by 2002:a05:6402:4cb:: with SMTP id n11mr35462928edw.292.1626716287650; Mon, 19 Jul 2021 10:38:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626716287; cv=none; d=google.com; s=arc-20160816; b=ffzrWYcYOdzMmLj8ykgb9fiBO4cM3t+z65feqN4nOcB0Dg+Ao4QshtW8BayRp570F5 hyQ/COl6Bvjme4tD0m8VsrpBxQlNrA3a6/F7NuDou8zKCKyjXIUGOPtsZS8tXT/pCw2r u98PBjQHAOClG5Lx/iR2mOaO7aZOvP9US75qqW+Rv9U4P6GciOLZGVh4RQXr3CAPr1Ua z0ORdJpXfi/OBOG5tfDdbZM7m6/5zOKP7tATJZyACBiBpSEcLslyDaUL3nTEDi/c5+7y eihgSJHqucccsyZMcn2J1ogd07Wm/tUlBVXFdRuadJBLqc+OTC/NW6Bj9YAe9iIR9c86 Jk0A== 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=d3d7FppR25hrEbNwBqQVn9cCPzSbaFvytc2eEGaBcHE=; b=fjfW6nnXZGe8RBvKW4MBqL9AVxSbVky/1e00MlaO/55a08h233BdiyV8FyYECF+NFk MMuAZMRqJ2aWxfoPuuxFtshWyhOxmnTFe2JTiV0B7PYZkZ0ozmiN/sVw1lFMQvcqnnNE fH/80nNe/7ww05zEhmkUTXxV3EHWOzQ4/PJYtIm3GJujETwXTaeTa+7k9xAgEU6TbaWG Fbsz31Qmm4aI7vF4rW4bQk5ABPgrpQgZz1JI6OhtwRyU7kLNtifDlzT2ODleBzJKRbhR Us3QLMbalTe3mkziq+RtzYdyJYC5UNWh9TLReoUSr2cY6IYBaRda2+1CVvPV4AlqghlR M3rg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=gB5Z7gwR; 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 w11si26915795ejc.221.2021.07.19.10.37.45; Mon, 19 Jul 2021 10:38:07 -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=gB5Z7gwR; 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 S1357977AbhGSQwl (ORCPT + 99 others); Mon, 19 Jul 2021 12:52:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:57556 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347816AbhGSPVe (ORCPT ); Mon, 19 Jul 2021 11:21:34 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 50BC861289; Mon, 19 Jul 2021 15:59:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626710346; bh=/CLhTyXPjjLRNb07GDJOFxKmUnEMQlQ76RxjoNskkSI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=gB5Z7gwRCSAD/1w42W9UBx9RK5XP7XzUz7O4e5aPdtOhkWYQ8hGHdHKtdxlSDLS4h fJHVEzjfQqL99697BWbR+GR4eRsSqJ4a4as3amB1/URuCrARc65PvpvXXaEsUo2mLl tyvIVLUJofJVOkNusiVEuBmgIlwc3egBx0Y+pQ0c= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Maurizio Lombardi , Sagi Grimberg , Christoph Hellwig , Sasha Levin Subject: [PATCH 5.10 177/243] nvme-tcp: cant set sk_user_data without write_lock Date: Mon, 19 Jul 2021 16:53:26 +0200 Message-Id: <20210719144946.614584990@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210719144940.904087935@linuxfoundation.org> References: <20210719144940.904087935@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: Maurizio Lombardi [ Upstream commit 0755d3be2d9bb6ea38598ccd30d6bbaa1a5c3a50 ] The sk_user_data pointer is supposed to be modified only while holding the write_lock "sk_callback_lock", otherwise we could race with other threads and crash the kernel. we can't take the write_lock in nvmet_tcp_state_change() because it would cause a deadlock, but the release_work queue will set the pointer to NULL later so we can simply remove the assignment. Fixes: b5332a9f3f3d ("nvmet-tcp: fix incorrect locking in state_change sk callback") Signed-off-by: Maurizio Lombardi Reviewed-by: Sagi Grimberg Signed-off-by: Christoph Hellwig Signed-off-by: Sasha Levin --- drivers/nvme/target/tcp.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/nvme/target/tcp.c b/drivers/nvme/target/tcp.c index 4df4f37e6b89..dedcb7aaf0d8 100644 --- a/drivers/nvme/target/tcp.c +++ b/drivers/nvme/target/tcp.c @@ -1467,7 +1467,6 @@ static void nvmet_tcp_state_change(struct sock *sk) case TCP_CLOSE_WAIT: case TCP_CLOSE: /* FALLTHRU */ - sk->sk_user_data = NULL; nvmet_tcp_schedule_release_queue(queue); break; default: -- 2.30.2