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

Daniel Wagner dwagner at suse.de
Tue Oct 20 06:10:11 PDT 2026


On Mon, Oct 19, 2026 at 02:26:30PM -0700, Mohamed Khalfella wrote:
>  Description:
>  		Shows the current state of the controller. Possible values:
> -		"new", "live", "resetting", "connecting", "deleting",
> -		"deleting (no IO)", "dead".
> +		"new", "live", "fencing", "fenced", "resetting", "connecting",
> +		"deleting", "deleting (no IO)", "dead".
> 
>  What:		/sys/class/nvme/nvmeX/numa_node
>  Date:		November 2018
> 
> 
> How about a diff like the one above? Similar to CIRN and CIU, I am not
> sure what to put in "KernelVersion".

I think the KernelVersion is when it first appeared. I would leave it as
it is and instead extend the description

  		Shows the current state of the controller. Possible values:
 		"new", "live", "resetting", "connecting", "deleting",
 		"deleting (no IO)", "dead".
        v7.5 introduced additionally:
        "fencing", "fenced"

Obviously, this is not idea. If someone starts to complain we might have
to filter out these two new states.



More information about the Linux-nvme mailing list