[PATCH v6 07/18] nvme: Introduce FENCING and FENCED controller states

[Daniel Wagner]

On Mon, Oct 19, 2026 at 07:01:38PM +0200, Daniel Wagner wrote:
> > --- a/drivers/nvme/host/sysfs.c
> > +++ b/drivers/nvme/host/sysfs.c
> > @@ -542,6 +542,8 @@ static ssize_t nvme_sysfs_show_state(struct device *dev,
> >  	static const char *const state_name[] = {
> >  		[NVME_CTRL_NEW]		= "new",
> >  		[NVME_CTRL_LIVE]	= "live",
> > +		[NVME_CTRL_FENCING]	= "fencing",
> > +		[NVME_CTRL_FENCED]	= "fenced",
> >  		[NVME_CTRL_RESETTING]	= "resetting",
> >  		[NVME_CTRL_CONNECTING]	= "connecting",
> >  		[NVME_CTRL_DELETING]	= "deleting",
> 
> The ABI documentation needs to be updated.

And while you’re at it, what’s the impact on blktests? I can’t quite
recall what you presented during ALPSS regarding blktests. Is this
covered?

Keith, Christoph, and I are mostly concerned about this patch.
Experience tells us that anyone touching the state machine will
introduce regressions. Because of that, I’d really like to make sure the
upstream testing side is covered. I know you’ve run tests in your lab,
but we need test cases that everyone can execute in their own
environments, and blktests is the right vehicle for that.