From: Nilay Shroff <nilay@linux.ibm.com>
To: John Garry <john.g.garry@oracle.com>,
shinichiro.kawasaki@wdc.com, linux-block@vger.kernel.org
Cc: hch@lst.de, linux-nvme@lists.infradead.org, dwagner@suse.de,
John Garry <john.garry@linux.dev>
Subject: Re: [PATCH v4] nvme/069: add a test for multipath cdev lifetime
Date: Thu, 16 Jul 2026 20:46:17 +0530 [thread overview]
Message-ID: <a4f4f444-967f-43a8-becf-465a3007ade8@linux.ibm.com> (raw)
In-Reply-To: <20260716082927.4053505-1-john.g.garry@oracle.com>
On 7/16/26 1:59 PM, John Garry wrote:
> +#include <inttypes.h>
> +#include <sys/ioctl.h>
> +#include <linux/types.h>
> +
> +#ifndef _LINUX_NVME_IOCTL_H
> +#define _LINUX_NVME_IOCTL_H
> +#define NVME_IOCTL_ID _IO('N', 0x40)
> +#endif /* _UAPI_LINUX_NVME_IOCTL_H */
> +
> +int main(int argc, char **argv)
> +{
> + int fd, fd1;
> + int count;
> +
> + if (argc < 2) {
> + fprintf(stderr, "usage: %s /dev/ngXnX", argv[0]);
> + return EINVAL;
> + }
> +
> + fd = open(argv[1], O_RDONLY);
> + if (fd < 0)
> + return fd;
> +
> + /*
> + * Steps:
> + * a. Signal to parent that we have opened the file so that it may
> + * start the teardown.
> + * b. Try to open device until disallowed/gone.
> + * c. Sleep to allow nvme-subsystem be torn down.
> + * d. Issue the ioctl on original fd.
> + */
> + kill(getppid(), SIGUSR2);
> + count = 0;
> + for (;;) {
> + fd1 = open(argv[1], O_RDONLY);
> + usleep(500000);
> + if (fd1 < 0)
> + break;
Does it make sense to check for errno set to ENODEV or ENOENT
before breaking out here?
Thanks,
--Nilay
next prev parent reply other threads:[~2026-07-16 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 8:29 [PATCH v4] nvme/069: add a test for multipath cdev lifetime John Garry
2026-07-16 15:16 ` Nilay Shroff [this message]
2026-07-16 16:36 ` John Garry
2026-07-17 7:00 ` Nilay Shroff
2026-07-17 9:06 ` John Garry
2026-07-17 9:49 ` Nilay Shroff
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=a4f4f444-967f-43a8-becf-465a3007ade8@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=dwagner@suse.de \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=john.garry@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.com \
/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