From: Eric Dumazet <eric.dumazet@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: netfilter-devel@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>,
nicolas prochazka <prochazka.nicolas@gmail.com>,
KVM list <kvm@vger.kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Re: Possible netfilter-related memory corruption in 2.6.37
Date: Mon, 14 Feb 2011 16:11:23 +0100 [thread overview]
Message-ID: <1297696283.2996.33.camel@edumazet-laptop> (raw)
In-Reply-To: <4D594313.4050009@redhat.com>
Le lundi 14 février 2011 à 16:58 +0200, Avi Kivity a écrit :
> We see severe memory corruption in kvm while used in conjunction with
> bridge/netfilter. Enabling slab debugging points the finger at a
> netfilter chain invoked from the bridge code.
>
> Can someone take a look?
>
> https://bugzilla.kernel.org/show_bug.cgi?id=27052
>
CC netdev
Does a revert of commit ca44ac386181ba7 help a bit ?
(net: don't reallocate skb->head unless the current one hasn't the
needed extra size or is shared)
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2011-02-14 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D594313.4050009@redhat.com>
2011-02-14 15:11 ` Eric Dumazet [this message]
2011-02-14 15:18 ` Possible netfilter-related memory corruption in 2.6.37 Jan Engelhardt
2011-02-14 15:50 ` Eric Dumazet
2011-02-14 16:24 ` Patrick McHardy
2011-02-14 16:29 ` Eric Dumazet
2011-02-14 16:37 ` Patrick McHardy
2011-02-14 16:48 ` Eric Dumazet
2011-02-14 16:52 ` Patrick McHardy
2011-02-18 18:37 ` Patrick McHardy
2011-02-18 19:14 ` Eric Dumazet
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=1297696283.2996.33.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=prochazka.nicolas@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox