From: Benny Halevy <bhalevy@tonian.com>
To: fanchaoting <fanchaoting@cn.fujitsu.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] ctl: should return NULL when dmsetup fail in find_dm_name
Date: Mon, 25 Mar 2013 11:34:16 +0200 [thread overview]
Message-ID: <51501A18.7050504@tonian.com> (raw)
In-Reply-To: <513DC8BF.5060503@cn.fujitsu.com>
On 2013-03-11 14:06, fanchaoting wrote:
> when dmsetup fail in find_dm_name, it should return NULL,if don't
> do it. it will cause core dump in get_dm when do free(name).
Thanks, but what version are you using?
This was already fixed here:
http://git.linux-nfs.org/?p=bhalevy/pnfsd-block-ctl.git;a=commitdiff;h=9082efe1dc12248e530d4200d7150a286abea922
Please update to the latest version
git://linux-nfs.org/~bhalevy/pnfsd-block-ctl.git
Benny
>
> Signed-off-by: fanchaoting<fanchaoting@cn.fujitsu.com>
>
> ---
> ctl.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/ctl.c b/ctl.c
> index 2071b0e..0ac1c44 100644
> --- a/ctl.c
> +++ b/ctl.c
> @@ -489,7 +489,7 @@ find_dm_name(int major, int minor)
> if (((fd = get_output("/sbin/dmsetup", argv)) == -1) ||
> ((fp = fdopen(fd, "r")) == NULL)) {
> printf("%s: get_output/fdopen failed\n", __func__);
> - return;
> + return NULL;
> }
> while (fgets(buf, sizeof (buf), fp) != NULL) {
> t = __token_init(buf, '\t');
> --
> 1.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-03-25 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 12:06 [PATCH] ctl: should return NULL when dmsetup fail in find_dm_name fanchaoting
2013-03-25 9:34 ` Benny Halevy [this message]
2013-03-25 10:03 ` fanchaoting
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=51501A18.7050504@tonian.com \
--to=bhalevy@tonian.com \
--cc=fanchaoting@cn.fujitsu.com \
--cc=linux-nfs@vger.kernel.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.