[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB5PR0701MB1958A4384C0B9C0571BD1DF99A1C0@DB5PR0701MB1958.eurprd07.prod.outlook.com>
Date: Sun, 23 Apr 2017 13:33:09 +0000
From: Jon Maloy <jon.maloy@...csson.com>
To: Pan Bian <bianpan2016@....com>, Ying Xue <ying.xue@...driver.com>,
"David S. Miller" <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"tipc-discussion@...ts.sourceforge.net"
<tipc-discussion@...ts.sourceforge.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/1] tipc: check return value of nlmsg_new
Acknowledged. Thank you for doing this job.
///jon
> -----Original Message-----
> From: Pan Bian [mailto:bianpan2016@....com]
> Sent: Sunday, April 23, 2017 03:09 AM
> To: Jon Maloy <jon.maloy@...csson.com>; Ying Xue
> <ying.xue@...driver.com>; David S. Miller <davem@...emloft.net>
> Cc: netdev@...r.kernel.org; tipc-discussion@...ts.sourceforge.net; linux-
> kernel@...r.kernel.org; Pan Bian <bianpan2016@....com>
> Subject: [PATCH 1/1] tipc: check return value of nlmsg_new
>
> Function nlmsg_new() will return a NULL pointer if there is no enough
> memory, and its return value should be checked before it is used.
> However, in function tipc_nl_node_get_monitor(), the validation of the
> return value of function nlmsg_new() is missed. This patch fixes the bug.
>
> Signed-off-by: Pan Bian <bianpan2016@....com>
> ---
> net/tipc/node.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/net/tipc/node.c b/net/tipc/node.c index 4512e83..568e48d 100644
> --- a/net/tipc/node.c
> +++ b/net/tipc/node.c
> @@ -2098,6 +2098,8 @@ int tipc_nl_node_get_monitor(struct sk_buff *skb,
> struct genl_info *info)
> int err;
>
> msg.skb = nlmsg_new(NLMSG_GOODSIZE, GFP_KERNEL);
> + if (!msg.skb)
> + return -ENOMEM;
> msg.portid = info->snd_portid;
> msg.seq = info->snd_seq;
>
> --
> 1.9.1
>
Powered by blists - more mailing lists