From: Massimo Cetra <ctrix+debianbugs@navynet.it>
To: Lin Ming <mlin@ss.pku.edu.cn>
Cc: Massimo Cetra <ctrix+debianbugs@navynet.it>,
Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org, Stephen Hemminger <shemminger@vyatta.com>,
"David S. Miller" <davem@davemloft.net>,
Julian Anastasov <ja@ssi.bg>
Subject: Re: [RFC PATCH] bridge: netfilter: fix skb->nf_bridge NULL panic in br_nf_forward_finish
Date: Mon, 09 Jul 2012 11:26:38 +0200 [thread overview]
Message-ID: <4FFAA3CE.1090504@navynet.it> (raw)
In-Reply-To: <1341584394.4789.34.camel@chief-river-32>
On 06/07/2012 16:19, Lin Ming wrote:
> I can reproduce similiar panic with 3.5-rc5 kernel as Massimo reported at:
> http://marc.info/?l=linux-netdev&m=134089242113979&w=2
>
> The steps to reproduce as follow,
>
> 1. On Host1, setup brige br0(192.168.1.106)
> 2. Boot a kvm guest(192.168.1.105) on Host1 and start httpd
> 3. Start IPVS service on Host1
> ipvsadm -A -t 192.168.1.106:80 -s rr
> ipvsadm -a -t 192.168.1.106:80 -r 192.168.1.105:80 -m
> 4. Run apache benchmark on Host2(192.168.1.101)
> ab -n 1000 http://192.168.1.106/
Thank you Lin,
i spent a couple of days trying to figure out how to reproduce but you
were quicker and smarter than me.
Massimo
next prev parent reply other threads:[~2012-07-09 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 14:19 [RFC PATCH] bridge: netfilter: fix skb->nf_bridge NULL panic in br_nf_forward_finish Lin Ming
2012-07-06 15:06 ` Eric Dumazet
2012-07-06 15:37 ` Lin Ming
2012-07-06 20:34 ` Julian Anastasov
2012-07-09 9:26 ` Massimo Cetra [this message]
2012-07-09 12:00 ` Lin Ming
2012-07-10 6:58 ` Massimo Cetra
2012-07-10 8:34 ` Lin Ming
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=4FFAA3CE.1090504@navynet.it \
--to=ctrix+debianbugs@navynet.it \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=ja@ssi.bg \
--cc=mlin@ss.pku.edu.cn \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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.