[PATCHv2 blktests 2/2] nvme: add test for writing to file-ns just after disabling it

[Shinichiro Kawasaki]

On Dec 05, 2024 / 12:20, Daniel Wagner wrote:
> On Thu, Dec 05, 2024 at 04:36:26PM +0530, Nilay Shroff wrote:
> > Sure, you may refer "5.27.1.8 Asynchronous Event Configuration (Feature Identifier 0Bh)"
> > in NVMe base spec 2.0. And then refer Figure 236, Namespace Attribute
> > Notices:
> 
>   Attached Namespace Attribute Notices (NAN): This bit determines
>   whether an asynchronous event notification is sent to the host for an
>   Attached Namespace Attribute Changed asynchronous event (refer to
>   Figure 151). If this bit is set to ‘1’, then the Attached Namespace
>   Attribute Changed asynchronous event is sent to the host when this
>   condition occurs. If this bit is cleared to ‘0’, then the controller
>   shall not send the Attached Namespace Attribute Changed asynchronous
>   event to the host.
> 
> I agree, doesn't say that the controller always has to send a NAN AEN.

Thanks for the discussion. IIUC, the users may have the NVME control which
does not send a NAN AEN. In that case, the environment has same set up as
this test case prepares. So this test does not look so weird for me.