On Tue, Jun 20, 2023 at 05:07:43PM +0300, Sagi Grimberg wrote:
>
> > When the host has enabled the udev/systemd autoconnect services for the
> > fc transport it interacts with blktests and make tests break.
> >
> > nvme-cli learned to ignore connects attemps when using the
> > --context command line option paired with a volatile configuration. Thus
> > we can mark all the resources created by blktests and avoid any
> > interaction with the systemd autoconnect scripts.
>
> Hmm... is this hapenning with non-fc as well?
I haven't seen a problem for TCP or RDMA yet but in principle it should also
exists. I can do some tracing to see if we have also problem thern. Two of the
udev rule match on the subsystem and the event type.
> > +_nvme_cli_supports_context() {
> > + if ! nvme connect --help 2>&1 | grep -q context > /dev/null; then
> > + return 1
> > + fi
> > + return 0
> > +}
>
> Not a great way to check support.
Yeah, agree, it's a bit dodgy. I'll try to figure out a different way. Any
suggestions?
