From: David Miller <davem@davemloft.net>
To: ja@ssi.bg
Cc: kaber@trash.net, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org, kswamy@barracuda.com
Subject: Re: [PATCH] netfilter: avoid double free in nf_reinject
Date: Sun, 07 Aug 2011 22:11:58 -0700 (PDT) [thread overview]
Message-ID: <20110807.221158.636741102851927559.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1108051326300.1494@ja.ssi.bg>
From: Julian Anastasov <ja@ssi.bg>
Date: Fri, 5 Aug 2011 13:36:28 +0300 (EEST)
>
> NF_STOLEN means skb was already freed
>
> Signed-off-by: Julian Anastasov <ja@ssi.bg>
> ---
>
> May be fixes IPVS+ip_queue problem reported by Kumar Swamy:
>
> http://marc.info/?l=linux-virtual-server&m=131098073717449&w=2
Since the netfilter maintainers are taking too damn long to integrate
bug fixes (and this has been happening for months), I'm going to apply
this directly.
Thanks Julian.
next prev parent reply other threads:[~2011-08-08 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 10:36 [PATCH] netfilter: avoid double free in nf_reinject Julian Anastasov
2011-08-08 5:11 ` David Miller [this message]
2011-08-08 10:13 ` Jan Engelhardt
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=20110807.221158.636741102851927559.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ja@ssi.bg \
--cc=kaber@trash.net \
--cc=kswamy@barracuda.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/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