From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andrei Vagin <avagin@virtuozzo.com>
Cc: Liping Zhang <zlpnobody@163.com>,
netfilter-devel@vger.kernel.org,
Liping Zhang <zlpnobody@gmail.com>,
Davide Caratti <dcaratti@redhat.com>
Subject: Re: [nf] netfilter: nf_ct_dccp/sctp: fix memory leak after netns cleanup
Date: Thu, 29 Jun 2017 01:36:30 +0200 [thread overview]
Message-ID: <20170628233630.GE4803@salvia> (raw)
In-Reply-To: <20170628182408.GA13678@outlook.office365.com>
On Wed, Jun 28, 2017 at 11:24:09AM -0700, Andrei Vagin wrote:
> Hi,
>
> We met the same issue in 4.12-rc7. Is there any chanse to push this
> patch to Linus' tree before the v4.12?
Very late, I'm expecting no -rc8 so I suspect not getting in time. But
I will drive this to -stable so this hits v4.12.x.
prev parent reply other threads:[~2017-06-28 23:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 11:17 [PATCH nf] netfilter: nf_ct_dccp/sctp: fix memory leak after netns cleanup Liping Zhang
2017-06-05 8:09 ` Davide Caratti
2017-06-19 15:52 ` Florian Westphal
2017-06-27 15:57 ` Pablo Neira Ayuso
2017-06-28 18:24 ` [nf] " Andrei Vagin
2017-06-28 23:36 ` Pablo Neira Ayuso [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=20170628233630.GE4803@salvia \
--to=pablo@netfilter.org \
--cc=avagin@virtuozzo.com \
--cc=dcaratti@redhat.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=zlpnobody@163.com \
--cc=zlpnobody@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.