All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davide Caratti <dcaratti@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net] net/sched: fix NULL dereference in the error path of tcf_vlan_init()
Date: Thu, 15 Mar 2018 15:29:09 +0100	[thread overview]
Message-ID: <1521124149.2797.11.camel@redhat.com> (raw)
In-Reply-To: <20180315142157.GG2130@nanopsycho>

On Thu, 2018-03-15 at 15:21 +0100, Jiri Pirko wrote:
...

> Acked-by: Jiri Pirko <jiri@mellanox.com>

thank you for reviewing!

apparently, also act_tunnel_key seem and act_csum have a similar problem.
I will check and eventually do a followup series this afternoon.

thank you,
regards
-- 
davide

  reply	other threads:[~2018-03-15 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 14:06 [PATCH net] net/sched: fix NULL dereference in the error path of tcf_vlan_init() Davide Caratti
2018-03-15 14:21 ` Jiri Pirko
2018-03-15 14:29   ` Davide Caratti [this message]
2018-03-15 22:21     ` Davide Caratti
2018-03-15 14:28 ` Roman Mashak

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=1521124149.2797.11.camel@redhat.com \
    --to=dcaratti@redhat.com \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.