From nobody Fri Dec 19 20:14:13 2025 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 9D714182EFF; Sun, 24 Mar 2024 23:49:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711324184; cv=none; b=Yfb4wS0aX3A2tocqCCp2h/ijZdG1O4AZuyhOLYFXa2moA8DPMB4/HaYwbhQgrOOBSGcOlhhMZ6ToEMAD2aW6lq7exaxCvZ0NVgo0GAq9MQZm1yKVXJo7zre4CVcw9uFZmcIXQMbsPtIXJynb5na0NM53xe3uI/0KungO2KMx0mQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711324184; c=relaxed/simple; bh=Zx4FbCVNw5xSF8GjY5g+ReLvwcTy3T4vitIDT4pNMlI=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=n3gTukPpGakY4ngEt38+rt/8/dRAAp318qfQoh66i5pIZpVkQY4Jbjc01EfM867doqG1KqwesnKgu1PomtxZKvsDbxMkP+Efm/ioGzl1oQ897LridtfyCmYxND8+A94tzPYATft6wWVlJXisdOWA2tzGT0HmJmC8lkVQIo+Mi5U= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=bwSVE3Xr; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="bwSVE3Xr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5F02FC433C7; Sun, 24 Mar 2024 23:49:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1711324183; bh=Zx4FbCVNw5xSF8GjY5g+ReLvwcTy3T4vitIDT4pNMlI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=bwSVE3XrRFpG4d6I1yrlrBS9WTOB8eG7wfSVOpJGwQu9qtrVT9jH5OJzkyDyCxawK cB0o2aGjWW/FdnUCDm4aKegX2SKu915dnarIPuOxophpvvvG99BCMYnKMD3Vi6gGgS qFnuGkdRLXFnWQTehBdZL6JMIp7eTMrKAp0a6oCjRuiXehrpUJ1JbTd3zXQ8gcVgXr hAcvKOY/JU8egphOthe4vHsmnwC6vhcyndnGnVAW9A9GwkALQFDtK4dyfe+JrKxtZ/ nw3aWfbR92cdMn2hz8dhM1PUCUjjNc2nWlXIQebImn/6ug/66xX2zTazKDjR4v+Ju5 ppkmubFm12NdQ== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Yewon Choi , Michal Kubiak , Paolo Abeni , Sasha Levin Subject: [PATCH 5.4 173/183] rds: introduce acquire/release ordering in acquire/release_in_xmit() Date: Sun, 24 Mar 2024 19:46:26 -0400 Message-ID: <20240324234638.1355609-174-sashal@kernel.org> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240324234638.1355609-1-sashal@kernel.org> References: <20240324234638.1355609-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" From: Yewon Choi [ Upstream commit 1422f28826d2a0c11e5240b3e951c9e214d8656e ] acquire/release_in_xmit() work as bit lock in rds_send_xmit(), so they are expected to ensure acquire/release memory ordering semantics. However, test_and_set_bit/clear_bit() don't imply such semantics, on top of this, following smp_mb__after_atomic() does not guarantee release ordering (memory barrier actually should be placed before clear_bit()). Instead, we use clear_bit_unlock/test_and_set_bit_lock() here. Fixes: 0f4b1c7e89e6 ("rds: fix rds_send_xmit() serialization") Fixes: 1f9ecd7eacfd ("RDS: Pass rds_conn_path to rds_send_xmit()") Signed-off-by: Yewon Choi Reviewed-by: Michal Kubiak Link: https://lore.kernel.org/r/ZfQUxnNTO9AJmzwc@libra05 Signed-off-by: Paolo Abeni Signed-off-by: Sasha Levin --- net/rds/send.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/net/rds/send.c b/net/rds/send.c index 6c2c5667e3a39..c0cebf4b4fe56 100644 --- a/net/rds/send.c +++ b/net/rds/send.c @@ -103,13 +103,12 @@ EXPORT_SYMBOL_GPL(rds_send_path_reset); =20 static int acquire_in_xmit(struct rds_conn_path *cp) { - return test_and_set_bit(RDS_IN_XMIT, &cp->cp_flags) =3D=3D 0; + return test_and_set_bit_lock(RDS_IN_XMIT, &cp->cp_flags) =3D=3D 0; } =20 static void release_in_xmit(struct rds_conn_path *cp) { - clear_bit(RDS_IN_XMIT, &cp->cp_flags); - smp_mb__after_atomic(); + clear_bit_unlock(RDS_IN_XMIT, &cp->cp_flags); /* * We don't use wait_on_bit()/wake_up_bit() because our waking is in a * hot path and finding waiters is very rare. We don't want to walk --=20 2.43.0