From: Christoph Hellwig <hch@lst.de>
To: javier@javigon.com
Cc: sagi@grimberg.me, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, minwoo.im.dev@gmail.com,
kbusch@kernel.org, "Javier González" <javier.gonz@samsung.com>,
hch@lst.de
Subject: Re: [PATCH V5 1/2] nvme: enable char device per namespace
Date: Wed, 24 Feb 2021 17:44:43 +0100 [thread overview]
Message-ID: <20210224164443.GA11338@lst.de> (raw)
In-Reply-To: <20210222190107.8479-2-javier.gonz@samsung.com>
> +static inline bool nvme_dev_is_generic(struct device *dev)
> +{
> + return dev->class == nvme_ns_class;
> +}
> +
> +static inline bool nvme_ns_is_generic(struct nvme_ns *ns)
> +{
> + return !!ns->minor;
> +}
What does is_generic mean here? In doubt add a few comments..
> /* some standard values */
> @@ -2241,6 +2270,13 @@ static int nvme_update_ns_info(struct nvme_ns *ns, struct nvme_id_ns *id)
> return 0;
>
> out_unfreeze:
> + /*
> + * When the device does not support any of the features required by the
> + * kernel (or viceversa), hide the block device. We can still rely on
> + * the namespace char device for submitting IOCTLs
> + */
> + ns->disk->flags |= GENHD_FL_HIDDEN;
> +
The out_unfreeze case also handles all kinds of real error, so this needs
to move into a better spot, and probably check a specific error code
or even explicit indicator.
> + struct nvme_ns *ns = container_of(inode->i_cdev, struct nvme_ns, cdev);
> +{
> + struct nvme_ns *ns = container_of(inode->i_cdev, struct nvme_ns, cdev);
> + struct nvme_ns *ns = container_of(file->f_inode->i_cdev,
> + struct nvme_ns, cdev);
Maybe add a little cdev_to_ns() helper?
> - if (nvme_update_ns_info(ns, id))
> - goto out_put_disk;
> + nvme_update_ns_info(ns, id);
I don't think we can simplify ignore all errors here.
> +static inline struct nvme_ns *nvme_get_ns_from_cdev(struct device *dev)
> +{
> + return dev_get_drvdata(dev);
> +}
I think we can keep this in core.c.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-02-24 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 19:01 [PATCH V5 0/2] nvme: enable char device per namespace javier
2021-02-22 19:01 ` [PATCH V5 1/2] " javier
2021-02-24 16:44 ` Christoph Hellwig [this message]
2021-02-24 20:28 ` Javier González
2021-02-22 19:01 ` [PATCH V5 2/2] nvme: allow open for nvme-generic char device javier
2021-02-24 16:45 ` Christoph Hellwig
2021-02-24 18:44 ` Minwoo Im
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=20210224164443.GA11338@lst.de \
--to=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=javier@javigon.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=minwoo.im.dev@gmail.com \
--cc=sagi@grimberg.me \
/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;
as well as URLs for NNTP newsgroup(s).