All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Tao Chen <boby.chen@huawei.com>, <konrad.wilk@oracle.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
	<wu.wubin@huawei.com>, <rudy.zhangmin@huawei.com>
Subject: Re: [PATCH] xen-blkback: enlarge the array size of blkback name
Date: Thu, 26 Mar 2015 12:23:10 +0100	[thread overview]
Message-ID: <5513EC1E.5090601@citrix.com> (raw)
In-Reply-To: <1426261941-32424-1-git-send-email-boby.chen@huawei.com>

El 13/03/15 a les 16.52, Tao Chen ha escrit:
> The blkback name is like blkback.domid.xvd[a-z], if domid has three digits
> (means larger than 100), then the backmost xvd wouldn't be fully shown.
> 
> Define a BLKBACK_NAME_LEN macro which is (TASK_COMM_LEN * 2), enlarge the
> array size of blkback name, so it will be fully shown in any case.
> 
> Signed-off-by: Tao Chen <boby.chen@huawei.com>
> ---
>  drivers/block/xen-blkback/xenbus.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/block/xen-blkback/xenbus.c b/drivers/block/xen-blkback/xenbus.c
> index e3afe97..0289e21 100644
> --- a/drivers/block/xen-blkback/xenbus.c
> +++ b/drivers/block/xen-blkback/xenbus.c
> @@ -21,6 +21,9 @@
>  #include <xen/grant_table.h>
>  #include "common.h"
>  
> +/* Enlarge the array size in order to fully show blkback name. */
> +#define BLKBACK_NAME_LEN (TASK_COMM_LEN * 2)

Any reason to use TASK_COMM_LEN instead of just coding it to 17? Or
maybe 20 to be on the safe side?

Roger.

  reply	other threads:[~2015-03-26 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 15:52 [PATCH] xen-blkback: enlarge the array size of blkback name Tao Chen
2015-03-26 11:23 ` Roger Pau Monné [this message]
2015-03-27  4:01   ` Chentao (Boby)
2015-03-27  4:01   ` Chentao (Boby)
2015-03-26 11:23 ` Roger Pau Monné
  -- strict thread matches above, loose matches on Subject: below --
2015-03-13 15:52 Tao Chen

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=5513EC1E.5090601@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=boby.chen@huawei.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rudy.zhangmin@huawei.com \
    --cc=wu.wubin@huawei.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.