Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3839349pxv; Mon, 19 Jul 2021 09:59:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzmHhMl8qVlXzfJE0UCroltwTEwM9GAdiGoc/TFnxkZq4ILDYIuQGIbI5Mu7eHilT0NGS4S X-Received: by 2002:aa7:d746:: with SMTP id a6mr35323826eds.296.1626713965229; Mon, 19 Jul 2021 09:59:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626713965; cv=none; d=google.com; s=arc-20160816; b=oxnq39n53sRoW8ZqQQYF6+/MPGeLYVPSKzuGf3kxwtJQ6B/3okewdvgIwRbk3hagrx TsS1418f12oQWPx7/koLCJ1BIAGJfkFwhC7ZCMkdbBfH9TvlAeNiFj4EZjYD882d3rG7 KnTQan7Oiyqp9PnjwNS5LMHXYfdTbVupwY1+SxlovVDFhlmi6V0w6qfBIHLMDtOOJ9Mp 0bnqJTSMAQqdOcCfoCqv7pdqMziWHbnXJ/OKMSnxN2kc3iRaKz9Q0k8ORQ92LOgP2l1D bdPagHzH0wSVrpkqYarV7K6nA5IPmlEMt1cba8fT1/4No2WvMuLfGJ1ZpylM0skNcQk5 Nruw== 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=qcZFG4lRAAdnaCpUC9LArbpobRtyk+5zuw7Q+4UWYyc=; b=dBhqwl2mUHomogZ8X7KxYePRYOg4DRrXl2rxKP4mVz1kgYGGlGybCemkwtPTD9Gs1V K/0m6bixpz22ift7hzTqwj9REJ43DE1HdqLVwDIlZaXrPkKB6hB9t3CbWWd9p7yooeHl OOCfpr7E4w5kYuyfNLFT2VjAe+eJUBc3brYrxPyi9aooWSCTrWCXtgdIeWkZ2YLDHRNm SkkcVYgPsASkPMsKZZXyvDthg8xaO9uuB92g+PghF8ihvjVQeRMLTN2WcToTUKv7MCsZ AcuY44++DFF3WkXQgQS7/qwvXjBUkIstpZNT8OlKdLqVZ49G2+Rs/LqysHKccwcquSmm xNNA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=EALweJno; 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 eg15si7593612edb.426.2021.07.19.09.59.02; Mon, 19 Jul 2021 09:59:25 -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=EALweJno; 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 S1351051AbhGSQNC (ORCPT + 99 others); Mon, 19 Jul 2021 12:13:02 -0400 Received: from mail.kernel.org ([198.145.29.99]:38958 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346052AbhGSPKA (ORCPT ); Mon, 19 Jul 2021 11:10:00 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 9F0EF61221; Mon, 19 Jul 2021 15:50:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626709818; bh=WF0TpTCVtD/q8bjs/VLUNrGERQsRQGf0gDxkGI0J854=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=EALweJnoTuoYJPHG0Ws2TjZX7RsRHoA/wNpu1nsTeeJJNzQdt0IyXsgcElXCTYBIv Po38tff61z2NvIdmNmphPpuy541tFg7TMmApGsiL8GlAmIizHy6l/0aXS6OZW8qJ3J JtNKAf8/bdSrCxXtejhYZa6aSgwWMuQ0MOgPvSMk= 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.4 111/149] nvme-tcp: cant set sk_user_data without write_lock Date: Mon, 19 Jul 2021 16:53:39 +0200 Message-Id: <20210719144927.643964494@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210719144901.370365147@linuxfoundation.org> References: <20210719144901.370365147@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 9bfd92b6677b..2ae846297d7c 100644 --- a/drivers/nvme/target/tcp.c +++ b/drivers/nvme/target/tcp.c @@ -1412,7 +1412,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