From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@wdc.com>,
linux-nvme@lists.infradead.org, Yi Zhang <yi.zhang@redhat.com>
Subject: Re: [PATCH] nvme-multipath: call del_gendisk() in nvme_mpath_check_last_path()
Date: Mon, 7 Jun 2021 11:46:14 +0200 [thread overview]
Message-ID: <afb8bb95-0b53-0dcf-89cb-7d96c91c2189@suse.de> (raw)
In-Reply-To: <20210603072244.GA4687@lst.de>
On 6/3/21 9:22 AM, Christoph Hellwig wrote:
>> +void nvme_mpath_check_last_path(struct nvme_ns *ns)
>> {
>> + struct nvme_ns_head *head = ns->head;
>> +
>> if (!head->disk)
>> return;
>> - if (head->disk->flags & GENHD_FL_UP) {
>> +
>> + if (list_empty(&head->list) && head->disk->flags & GENHD_FL_UP) {
>
> Please add the braces around the "&".
>
Ok.
>> nvme_cdev_del(&head->cdev, &head->cdev_device);
>> del_gendisk(head->disk);
>> }
>> +}
>
> Also it seems like we can just pass the head here, no need for ns.
>
Ok.
>> - if (head->disk && list_empty(&head->list))
>> - kblockd_schedule_work(&head->requeue_work);
>
> Did this get lost in the new version?
>
I had removed it as it'll be called from nvme_mpath_remove_disk()
anyway, but seeing that the refcount might induce a different lifetime
I'll be re-adding it.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, 90409 Nürnberg
GF: F. Imendörffer, HRB 36809 (AG Nürnberg)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-06-07 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 7:09 [PATCH] nvme-multipath: call del_gendisk() in nvme_mpath_check_last_path() Hannes Reinecke
2021-06-03 7:22 ` Christoph Hellwig
2021-06-03 7:31 ` Christoph Hellwig
2021-06-07 9:46 ` Hannes Reinecke [this message]
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=afb8bb95-0b53-0dcf-89cb-7d96c91c2189@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=keith.busch@wdc.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yi.zhang@redhat.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