From: Veaceslav Falico <vfalico@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Pravin B Shelar <pshelar@nicira.com>,
Daniel Borkmann <dborkman@redhat.com>
Subject: Re: gre: fix a possible skb leak
Date: Mon, 24 Jun 2013 16:39:30 +0200 [thread overview]
Message-ID: <20130624143930.GB28057@redhat.com> (raw)
In-Reply-To: <1372084560.3301.68.camel@edumazet-glaptop>
On Mon, Jun 24, 2013 at 07:36:00AM -0700, Eric Dumazet wrote:
>On Mon, 2013-06-24 at 16:03 +0200, Veaceslav Falico wrote:
>
>> Maybe we can also use it here (build-tested only):
>
>Sure, but it will be done later on net-next
>
>This patch is a stable candidate, so I made a somewhat minimal change
Makes sense, didn't realize that it's for net, not net-next.
Thank you!
>
>
>
next prev parent reply other threads:[~2013-06-24 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 13:26 [PATCH] gre: fix a possible skb leak Eric Dumazet
2013-06-24 14:03 ` Veaceslav Falico
2013-06-24 14:36 ` Eric Dumazet
2013-06-24 14:39 ` Veaceslav Falico [this message]
2013-06-24 14:38 ` Daniel Borkmann
2013-06-25 23:08 ` [PATCH] " David Miller
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=20130624143930.GB28057@redhat.com \
--to=vfalico@redhat.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=eric.dumazet@gmail.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).