From: Dave Jones <davej@redhat.com>
To: netdev@vger.kernel.org
Cc: Wensong Zhang <wensong@linuxvirtualserver.org>
Subject: ip_vs_ftp causing ip_vs oops on module load.
Date: Wed, 18 May 2011 16:19:15 -0400 [thread overview]
Message-ID: <20110518201915.GB20475@redhat.com> (raw)
I get this oops from ip_vs_ftp..
general protection fault: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
last sysfs file: /sys/module/nf_nat/refcnt
CPU 3
Modules linked in: ip_vs(+) libcrc32c nf_nat nfsd lockd nfs_acl auth_rpcgss sunrpc cpufreq_ondemand powernow_k8 freq_table mperf ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables snd_hda_codec_realtek ppdev snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm microcode edac_core snd_timer k10temp snd pcspkr usb_debug edac_mce_amd soundcore snd_page_alloc sp5100_tco i2c_piix4 parport_pc parport wmi r8169 mii lm63 ipv6 pata_acpi firewire_ohci ata_generic firewire_core crc_itu_t pata_atiixp floppy radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: nf_nat]
Pid: 1366, comm: modprobe Not tainted 2.6.39-rc7+ #15 Gigabyte Technology Co., Ltd. GA-MA78GM-S2H/GA-MA78GM-S2H
RIP: 0010:[<ffffffff8107bddb>] [<ffffffff8107bddb>] notifier_chain_register+0xb/0x2a
RSP: 0018:ffff880114139e68 EFLAGS: 00010206
RAX: 2f736e74656e2f74 RBX: ffffffffa04265d0 RCX: 0000000000000003
RDX: 00000000656e6567 RSI: ffffffffa04265d0 RDI: ffffffffa04235d8
RBP: ffff880114139e68 R08: ffff880114139df8 R09: 0000000000000001
R10: 0000000000000001 R11: 00000000000001cc R12: ffffffffa0432106
R13: 0000000000000000 R14: 0000000000007f0d R15: 0000000000410e40
FS: 00007f2aaf242720(0000) GS:ffff88012a800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f2aaea0100f CR3: 000000011424f000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 1366, threadinfo ffff880114138000, task ffff8801146cc7a0)
Stack:
ffff880114139e78 ffffffff8107be36 ffff880114139ec8 ffffffff81403058
0000000000000000 0000000000000000 ffff880114139ea8 0000000000000000
ffffffffa0432106 0000000000000000 0000000000007f0d 0000000000410e40
Call Trace:
[<ffffffff8107be36>] raw_notifier_chain_register+0xe/0x10
[<ffffffff81403058>] register_netdevice_notifier+0x2d/0x1b6
[<ffffffffa0432106>] ? ip_vs_conn_init+0x106/0x106 [ip_vs]
[<ffffffffa04322c7>] ip_vs_control_init+0xa5/0xce [ip_vs]
[<ffffffffa0432106>] ? ip_vs_conn_init+0x106/0x106 [ip_vs]
[<ffffffffa0432116>] ip_vs_init+0x10/0x11c [ip_vs]
[<ffffffff81002099>] do_one_initcall+0x7f/0x13a
[<ffffffff81096524>] sys_init_module+0x132/0x281
[<ffffffff814cc702>] system_call_fastpath+0x16/0x1b
Code: 07 ff c8 89 43 48 eb 08 48 89 df e8 dc 95 44 00 4c 89 e6 48 89 df e8 a7 a5 44 00 5b 41 5c 5d c3 55 48 89 e5 66 66 66 66 90 eb 0c <8b> 50 10 39 56 10 7f 0c 48 8d 78 08 48 8b 07 48 85 c0 75 ec 48
RIP [<ffffffff8107bddb>] notifier_chain_register+0xb/0x2a
RSP <ffff880114139e68>
---[ end trace e90d7053ad1a7a5b ]---
This script replicates the bug.
(it usually oopses after just a few loops)
#!/bin/sh
while [ 1 ];
do
modprobe ip_vs_ftp
modprobe -r ip_vs_ftp
done
Looks like something isn't getting cleaned up on module exit
that we fall over when we encounter it next time it gets loaded ?
Dave
next reply other threads:[~2011-05-18 20:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 20:19 Dave Jones [this message]
2011-05-19 1:10 ` ip_vs_ftp causing ip_vs oops on module load Simon Horman
2011-05-19 3:26 ` Simon Horman
2011-05-19 6:33 ` Julian Anastasov
2011-05-19 7:55 ` Simon Horman
2011-05-19 8:14 ` Hans Schillstrom
2011-05-19 8:15 ` Julian Anastasov
2011-05-19 7:58 ` Hans Schillstrom
2011-05-19 8:17 ` Simon Horman
2011-05-19 8:52 ` Hans Schillstrom
2011-05-19 7:52 ` Hans Schillstrom
2011-05-19 8:07 ` Simon Horman
2011-05-19 8:55 ` Julian Anastasov
2011-05-19 10:19 ` Hans Schillstrom
2011-05-19 20:13 ` Julian Anastasov
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=20110518201915.GB20475@redhat.com \
--to=davej@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=wensong@linuxvirtualserver.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;
as well as URLs for NNTP newsgroup(s).