From: Simon Horman <horms@verge.net.au>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: netdev <netdev@vger.kernel.org>,
lvs-devel@vger.kernel.org, Wensong Zhang <wensong@linux-vs.org>,
Julian Anastasov <ja@ssi.bg>
Subject: Re: ipvs oops in 3.0-rc7
Date: Thu, 21 Jul 2011 14:40:33 +0900 [thread overview]
Message-ID: <20110721054033.GA8299@verge.net.au> (raw)
In-Reply-To: <20110720205019.9dfa30c3.rdunlap@xenotime.net>
On Wed, Jul 20, 2011 at 08:50:19PM -0700, Randy Dunlap wrote:
> I'm seeing the following Oops in 3.0-rc7 on x86_64, just loading and unloading
> modules. Any chance this is already fixed? I can test current git, but I
> wanted to ask first.
>
> Looks like it is on the second module load of ip_vs (i.e.,
> modprobe ip_vs; rmmod ip_vs; modprobe ip_vs).
Hi Randy,
I don't believe that this problem has been resolved (or observed before).
next prev parent reply other threads:[~2011-07-21 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 3:50 ipvs oops in 3.0-rc7 Randy Dunlap
2011-07-21 5:40 ` Simon Horman [this message]
2011-07-21 8:42 ` Huajun Li
2011-07-21 17:26 ` Randy Dunlap
2011-07-21 9:04 ` Julian Anastasov
2011-07-21 13:37 ` Huajun Li
2011-07-22 0:08 ` Simon Horman
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=20110721054033.GA8299@verge.net.au \
--to=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=wensong@linux-vs.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