From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Joe Stringer <joestringer@nicira.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, pshelar@nicira.com
Subject: Re: [PATCHv3 net 2/6] openvswitch: Fix skb leak in ovs_fragment()
Date: Tue, 6 Oct 2015 17:12:08 +0300 [thread overview]
Message-ID: <5613D6B8.2080006@cogentembedded.com> (raw)
In-Reply-To: <1444083799-57090-3-git-send-email-joestringer@nicira.com>
Hello.
On 10/6/2015 1:23 AM, Joe Stringer wrote:
> If ovs_fragment() was unable to fragment the skb due to an L2 header
> that exceeds the supported length, skbs would be leaked. Fix the bug.
>
> Fixes: 7f8a436 "openvswitch: Add conntrack action"
12-digit SHA1 needed here. And parens along with double quotes as well.
> Signed-off-by: Joe Stringer <joestringer@nicira.com>
> Acked-by: Pravin B Shelar <pshelar@nicira.com>
MBR, Sergei
next prev parent reply other threads:[~2015-10-06 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 22:23 [PATCHv3 net 0/6] OVS conntrack fixes for net Joe Stringer
2015-10-05 22:23 ` [PATCHv3 net 1/6] openvswitch: Fix typos in CT headers Joe Stringer
2015-10-05 22:23 ` [PATCHv3 net 2/6] openvswitch: Fix skb leak in ovs_fragment() Joe Stringer
2015-10-06 14:12 ` Sergei Shtylyov [this message]
2015-10-06 18:01 ` Joe Stringer
2015-10-05 22:23 ` [PATCHv3 net 3/6] openvswitch: Ensure flow is valid before executing ct Joe Stringer
2015-10-05 22:23 ` [PATCHv3 net 4/6] openvswitch: Reject ct_state unsupported bits Joe Stringer
2015-10-05 22:23 ` [PATCHv3 net 5/6] openvswitch: Extend ct_state match field to 32 bits Joe Stringer
2015-10-05 22:23 ` [PATCHv3 net 6/6] openvswitch: Change CT_ATTR_FLAGS to CT_ATTR_COMMIT Joe Stringer
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=5613D6B8.2080006@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=joestringer@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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).