netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftnl PATCH 5/6] src/set_elem: Don't return garbage in nftnl_set_elems_parse()
Date: Fri, 15 Dec 2017 16:19:24 +0100	[thread overview]
Message-ID: <20171215151924.2ohfdod25v2uv2gl@salvia> (raw)
In-Reply-To: <20171214194025.21334-6-phil@nwl.cc>

On Thu, Dec 14, 2017 at 08:40:24PM +0100, Phil Sutter wrote:
> This might happen if netlink message is malformed (no nested attributes
> are present), so treat this as an error and return -1 instead of
> garbage to caller.

Applied, thanks.

  reply	other threads:[~2017-12-15 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 19:40 [libnftnl PATCH 0/6] Another round of Covscan indicated fixes Phil Sutter
2017-12-14 19:40 ` [libnftnl PATCH 1/6] nftnl_data_reg_snprintf: Add a missing break Phil Sutter
2017-12-15 15:17   ` Pablo Neira Ayuso
2017-12-14 19:40 ` [libnftnl PATCH 2/6] src/gen: Remove a pointless call to mnl_nlmsg_get_payload() Phil Sutter
2017-12-15 15:17   ` Pablo Neira Ayuso
2017-12-14 19:40 ` [libnftnl PATCH 3/6] src/object: Avoid returning garbage in nftnl_obj_do_parse() Phil Sutter
2017-12-15 15:18   ` Pablo Neira Ayuso
2017-12-14 19:40 ` [libnftnl PATCH 4/6] src/ruleset: Avoid reading garbage in nftnl_ruleset_cb() Phil Sutter
2017-12-15 15:18   ` Pablo Neira Ayuso
2017-12-14 19:40 ` [libnftnl PATCH 5/6] src/set_elem: Don't return garbage in nftnl_set_elems_parse() Phil Sutter
2017-12-15 15:19   ` Pablo Neira Ayuso [this message]
2017-12-14 19:40 ` [libnftnl PATCH 6/6] src/trace: Check return value of mnl_attr_parse_nested() Phil Sutter
2017-12-15 15:20   ` Pablo Neira Ayuso

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=20171215151924.2ohfdod25v2uv2gl@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=phil@nwl.cc \
    /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).