From: Dominique Martinet <asmadeus@codewreck.org>
To: piaojun <piaojun@huawei.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Greg Kurz <groug@kaod.org>,
Eric Van Hensbergen <ericvh@gmail.com>,
Ron Minnich <rminnich@sandia.gov>,
Latchesar Ionkov <lucho@ionkov.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH v3] net/9p/trans_virtio.c: add null terminal for mount tag
Date: Fri, 3 Aug 2018 11:42:57 +0200 [thread overview]
Message-ID: <20180803094257.GA21285@nautica> (raw)
In-Reply-To: <5B641ECC.5030401@huawei.com>
piaojun wrote on Fri, Aug 03, 2018:
> chan->tag is Non-null terminated which will result in printing messy code
> when debugging code. So we should add '\0' for tag to make the code more
> convenient and robust. In addition, I drop char->tag_len to simplify the
> code.
LGTM, I'll pick this up.
Thanks for the rework
> Signed-off-by: Jun Piao <piaojun@huawei.com>
> ---
> net/9p/trans_virtio.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/net/9p/trans_virtio.c b/net/9p/trans_virtio.c
> index d422bfc..46a5ab2 100644
> --- a/net/9p/trans_virtio.c
> +++ b/net/9p/trans_virtio.c
> @@ -89,10 +89,8 @@ struct virtio_chan {
> unsigned long p9_max_pages;
> /* Scatterlist: can be too big for stack. */
> struct scatterlist sg[VIRTQUEUE_NUM];
> -
> - int tag_len;
> /*
> - * tag name to identify a mount Non-null terminated
> + * tag name to identify a mount null terminated
> */
> char *tag;
>
> @@ -525,14 +523,15 @@ static ssize_t p9_mount_tag_show(struct device *dev,
> {
> struct virtio_chan *chan;
> struct virtio_device *vdev;
> + int tag_len;
>
> vdev = dev_to_virtio(dev);
> chan = vdev->priv;
> + tag_len = strlen(chan->tag);
>
> - memcpy(buf, chan->tag, chan->tag_len);
> - buf[chan->tag_len] = 0;
> + memcpy(buf, chan->tag, tag_len + 1);
>
> - return chan->tag_len + 1;
> + return tag_len + 1;
> }
>
> static DEVICE_ATTR(mount_tag, 0444, p9_mount_tag_show, NULL);
> @@ -585,7 +584,7 @@ static int p9_virtio_probe(struct virtio_device *vdev)
> err = -EINVAL;
> goto out_free_vq;
> }
> - tag = kmalloc(tag_len, GFP_KERNEL);
> + tag = kzalloc(tag_len + 1, GFP_KERNEL);
> if (!tag) {
> err = -ENOMEM;
> goto out_free_vq;
> @@ -594,7 +593,6 @@ static int p9_virtio_probe(struct virtio_device *vdev)
> virtio_cread_bytes(vdev, offsetof(struct virtio_9p_config, tag),
> tag, tag_len);
> chan->tag = tag;
> - chan->tag_len = tag_len;
> err = sysfs_create_file(&(vdev->dev.kobj), &dev_attr_mount_tag.attr);
> if (err) {
> goto out_free_tag;
> @@ -654,8 +652,7 @@ static int p9_virtio_probe(struct virtio_device *vdev)
>
> mutex_lock(&virtio_9p_lock);
> list_for_each_entry(chan, &virtio_chan_list, chan_list) {
> - if (!strncmp(devname, chan->tag, chan->tag_len) &&
> - strlen(devname) == chan->tag_len) {
> + if (!strcmp(devname, chan->tag)) {
> if (!chan->inuse) {
> chan->inuse = true;
> found = 1;
> --
prev parent reply other threads:[~2018-08-03 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 9:22 [PATCH v3] net/9p/trans_virtio.c: add null terminal for mount tag piaojun
2018-08-03 9:42 ` Dominique Martinet [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=20180803094257.GA21285@nautica \
--to=asmadeus@codewreck.org \
--cc=akpm@linux-foundation.org \
--cc=ericvh@gmail.com \
--cc=groug@kaod.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=piaojun@huawei.com \
--cc=rminnich@sandia.gov \
--cc=v9fs-developer@lists.sourceforge.net \
/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