From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Maninder Singh <maninder1.s@samsung.com>, kys@microsoft.com
Cc: haiyangz@microsoft.com, devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org, pankaj.m@samsung.com
Subject: Re: [PATCH 1/1] drivers: hv: hv_utils_transport: Fixing validation of correct pointer
Date: Fri, 03 Jul 2015 10:09:52 +0200 [thread overview]
Message-ID: <876161br1r.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1435902333-31308-1-git-send-email-maninder1.s@samsung.com> (Maninder Singh's message of "Fri, 03 Jul 2015 11:15:33 +0530")
Maninder Singh <maninder1.s@samsung.com> writes:
> cn_msg should be validated instead of msg after memory allocation.
>
Thanks,
This was already fixed by Dan:
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2015-May/070193.html
my Reviewed-by:
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2015-June/070599.html
but I don't see it in K. Y. recent submission to Greg. K. Y., could you
please pick it up?
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> Reviewed-by: Akhilesh Kumar <akhilesh.k@samsung.com>
> ---
> drivers/hv/hv_utils_transport.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hv/hv_utils_transport.c b/drivers/hv/hv_utils_transport.c
> index ea7ba5e..6a9d80a 100644
> --- a/drivers/hv/hv_utils_transport.c
> +++ b/drivers/hv/hv_utils_transport.c
> @@ -186,7 +186,7 @@ int hvutil_transport_send(struct hvutil_transport *hvt, void *msg, int len)
> return -EINVAL;
> } else if (hvt->mode == HVUTIL_TRANSPORT_NETLINK) {
> cn_msg = kzalloc(sizeof(*cn_msg) + len, GFP_ATOMIC);
> - if (!msg)
> + if (!cn_msg)
> return -ENOMEM;
> cn_msg->id.idx = hvt->cn_id.idx;
> cn_msg->id.val = hvt->cn_id.val;
--
Vitaly
next prev parent reply other threads:[~2015-07-03 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 5:45 [PATCH 1/1] drivers: hv: hv_utils_transport: Fixing validation of correct pointer Maninder Singh
2015-07-03 8:09 ` Vitaly Kuznetsov [this message]
2015-07-03 18:17 ` KY Srinivasan
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=876161br1r.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=pankaj.m@samsung.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