From: David Miller <davem@davemloft.net>
To: kjlu@umn.edu
Cc: pakki001@umn.edu, jon.maloy@ericsson.com, ying.xue@windriver.com,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: tipc: fix a missing check of nla_nest_start
Date: Sat, 16 Mar 2019 12:09:34 -0700 (PDT) [thread overview]
Message-ID: <20190316.120934.948765192267523842.davem@davemloft.net> (raw)
In-Reply-To: <20190315171200.5269-1-kjlu@umn.edu>
From: Kangjie Lu <kjlu@umn.edu>
Date: Fri, 15 Mar 2019 12:11:59 -0500
> nla_nest_start could fail and requires a check. The fix returns
> -EMSGSIZE if it fails.
>
> Signed-off-by: Kangjie Lu <kjlu@umn.edu>
Applied.
prev parent reply other threads:[~2019-03-16 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 6:07 [PATCH] net: tipc: fix a missing check of nla_nest_start Kangjie Lu
2019-03-15 8:58 ` Sergei Shtylyov
2019-03-15 17:11 ` Kangjie Lu
2019-03-16 19:09 ` David Miller [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=20190316.120934.948765192267523842.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pakki001@umn.edu \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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;
as well as URLs for NNTP newsgroup(s).