public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: pshelar@ovn.org, netdev@vger.kernel.org, dev@openvswitch.org,
	sthemmin@microsoft.com
Subject: Re: [PATCH net 0/2] openvswitch tests for nla_nest_start
Date: Fri, 20 Jul 2018 12:19:04 -0700 (PDT)	[thread overview]
Message-ID: <20180720.121904.1913959023397282097.davem@davemloft.net> (raw)
In-Reply-To: <20180720.121536.612580141999331732.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Fri, 20 Jul 2018 12:15:36 -0700 (PDT)

> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Wed, 18 Jul 2018 09:12:14 -0700
> 
>> Coverity is looking for bugs here, and a couple of new bugzilla
>> reports showed up where nla_nest_start return is not checked
>> for NULL.
> 
> Series applied and patch #2 queued up for -stable, thanks Stephen.

Actually, this wasn't compile tested and fails to build. :-/

Please fix this and resubmit.

Thanks.

      reply	other threads:[~2018-07-20 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 16:12 [PATCH net 0/2] openvswitch tests for nla_nest_start Stephen Hemminger
2018-07-18 16:12 ` [PATCH net 1/2] openvswitch: check for null return " Stephen Hemminger
     [not found]   ` <20180718161216.27820-2-sthemmin-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>
2018-07-19  6:49     ` Pravin Shelar
2018-07-18 16:12 ` [PATCH net 2/2] openvswitch: check for null return for nla_nest_start in datapath Stephen Hemminger
     [not found]   ` <20180718161216.27820-3-sthemmin-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>
2018-07-19  6:49     ` Pravin Shelar
2018-07-20 19:15 ` [PATCH net 0/2] openvswitch tests for nla_nest_start David Miller
2018-07-20 19:19   ` 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=20180720.121904.1913959023397282097.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@ovn.org \
    --cc=stephen@networkplumber.org \
    --cc=sthemmin@microsoft.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