public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
	Sasha Levin <sashal@kernel.org>,
	linux-nvme@lists.infradead.org
Subject: [PATCH AUTOSEL 5.15 14/19] nvme: introduce helper function to get ctrl state
Date: Mon, 11 Dec 2023 08:57:48 -0500	[thread overview]
Message-ID: <20231211135908.385694-14-sashal@kernel.org> (raw)
In-Reply-To: <20231211135908.385694-1-sashal@kernel.org>

From: Keith Busch <kbusch@kernel.org>

[ Upstream commit 5c687c287c46fadb14644091823298875a5216aa ]

The controller state is typically written by another CPU, so reading it
should ensure no optimizations are taken. This is a repeated pattern in
the driver, so start with adding a convenience function that returns the
controller state with READ_ONCE().

Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 drivers/nvme/host/nvme.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
index 590ffa3e1c497..e523427d8a581 100644
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -360,6 +360,11 @@ struct nvme_ctrl {
 	struct nvme_fault_inject fault_inject;
 };
 
+static inline enum nvme_ctrl_state nvme_ctrl_state(struct nvme_ctrl *ctrl)
+{
+	return READ_ONCE(ctrl->state);
+}
+
 enum nvme_iopolicy {
 	NVME_IOPOLICY_NUMA,
 	NVME_IOPOLICY_RR,
-- 
2.42.0


  parent reply	other threads:[~2023-12-11 14:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 13:57 [PATCH AUTOSEL 5.15 01/19] ASoC: wm8974: Correct boost mixer inputs Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 02/19] ASoC: Intel: Skylake: Fix mem leak in few functions Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 03/19] ASoC: nau8822: Fix incorrect type in assignment and cast to restricted __be16 Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 04/19] ASoC: Intel: Skylake: mem leak in skl register function Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 05/19] ASoC: cs43130: Fix the position of const qualifier Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 06/19] ASoC: cs43130: Fix incorrect frame delay configuration Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 07/19] ASoC: rt5650: add mutex to avoid the jack detection failure Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 08/19] ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not available Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 09/19] nouveau/tu102: flush all pdbs on vmm flush Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 10/19] ASoC: hdac_hda: Conditionally register dais for HDMI and Analog Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 11/19] net/tg3: fix race condition in tg3_reset_task() Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 12/19] ASoC: da7219: Support low DC impedance headset Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 13/19] ASoC: ops: add correct range check for limiting volume Sasha Levin
2023-12-11 13:57 ` Sasha Levin [this message]
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 15/19] mips/smp: Call rcutree_report_cpu_starting() earlier Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 16/19] drm/amdgpu: Add NULL checks for function pointers Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 17/19] drm/exynos: fix a potential error pointer dereference Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 18/19] drm/exynos: fix a wrong error checking Sasha Levin
2023-12-11 13:57 ` [PATCH AUTOSEL 5.15 19/19] hwmon: (corsair-psu) Fix probe when built-in Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231211135908.385694-14-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox