Skip to contentSkip to conversation

2.6.11-rc3 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840

DISCUSSION Frank van Maarseveen 2 participants 5 messages Feb 6, 2005 – Feb 14, 2005

lore
Share & tools
lore
#0 lore raw

While executing
iptables -t nat -D OUTPUT -d 80.126.170.174 -p tcp --dport https -j DNAT --to 192.168.0.1 iptables -t nat -D OUTPUT -d 80.126.170.174 -p tcp --dport http -j DNAT --to 192.168.0.1 ip route del default
ip addr del 80.126.170.174 dev eth0

on a dual PIII during a shutdown:

kernel: BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
kernel: caller is get_next_corpse+0x13/0x260
kernel:  [<c010385e>] dump_stack+0x1e/0x30
kernel:  [<c024f13f>] smp_processor_id+0xaf/0xc0
kernel:  [<c0407d83>] get_next_corpse+0x13/0x260
kernel:  [<c0408006>] ip_ct_iterate_cleanup+0x36/0xc0
kernel:  [<c041896a>] masq_inet_event+0x3a/0x70
kernel:  [<c012eded>] notifier_call_chain+0x2d/0x50
kernel:  [<c03ef589>] inet_del_ifa+0x99/0x150
kernel:  [<c03efafb>] inet_rtm_deladdr+0x12b/0x170
kernel:  [<c03b1f47>] rtnetlink_rcv+0x347/0x410
kernel:  [<c03c1b10>] netlink_data_ready+0x60/0x70
kernel:  [<c03c0f71>] netlink_sendskb+0x31/0x60
kernel:  [<c03c17e9>] netlink_sendmsg+0x259/0x310
kernel:  [<c039e87b>] sock_sendmsg+0xbb/0xe0
kernel:  [<c03a0424>] sys_sendmsg+0x1c4/0x230
kernel:  [<c03a08cc>] sys_socketcall+0x21c/0x240
kernel:  [<c01029f3>] syscall_call+0x7/0xb
kernel: BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
kernel: caller is get_next_corpse+0x23f/0x260
kernel:  [<c010385e>] dump_stack+0x1e/0x30
kernel:  [<c024f13f>] smp_processor_id+0xaf/0xc0
kernel:  [<c0407faf>] get_next_corpse+0x23f/0x260
kernel:  [<c0408006>] ip_ct_iterate_cleanup+0x36/0xc0
kernel:  [<c041896a>] masq_inet_event+0x3a/0x70
kernel:  [<c012eded>] notifier_call_chain+0x2d/0x50
kernel:  [<c03ef589>] inet_del_ifa+0x99/0x150
kernel:  [<c03efafb>] inet_rtm_deladdr+0x12b/0x170
kernel:  [<c03b1f47>] rtnetlink_rcv+0x347/0x410
kernel:  [<c03c1b10>] netlink_data_ready+0x60/0x70
kernel:  [<c03c0f71>] netlink_sendskb+0x31/0x60
kernel:  [<c03c17e9>] netlink_sendmsg+0x259/0x310
kernel:  [<c039e87b>] sock_sendmsg+0xbb/0xe0
kernel:  [<c03a0424>] sys_sendmsg+0x1c4/0x230
kernel:  [<c03a08cc>] sys_socketcall+0x21c/0x240
kernel:  [<c01029f3>] syscall_call+0x7/0xb
Signature · 1 line
Frank
#1 lore raw
Quoted 36 lines · Frank van Maarseveen

While executing
iptables -t nat -D OUTPUT -d 80.126.170.174 -p tcp --dport https -j DNAT --to 192.168.0.1 iptables -t nat -D OUTPUT -d 80.126.170.174 -p tcp --dport http -j DNAT --to 192.168.0.1 ip route del default
ip addr del 80.126.170.174 dev eth0

on a dual PIII during a shutdown:

kernel: BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
kernel: caller is get_next_corpse+0x13/0x260
kernel:  [<c010385e>] dump_stack+0x1e/0x30
kernel:  [<c024f13f>] smp_processor_id+0xaf/0xc0
kernel:  [<c0407d83>] get_next_corpse+0x13/0x260
kernel:  [<c0408006>] ip_ct_iterate_cleanup+0x36/0xc0
kernel:  [<c041896a>] masq_inet_event+0x3a/0x70
kernel:  [<c012eded>] notifier_call_chain+0x2d/0x50
kernel:  [<c03ef589>] inet_del_ifa+0x99/0x150
kernel:  [<c03efafb>] inet_rtm_deladdr+0x12b/0x170
kernel:  [<c03b1f47>] rtnetlink_rcv+0x347/0x410
kernel:  [<c03c1b10>] netlink_data_ready+0x60/0x70
kernel:  [<c03c0f71>] netlink_sendskb+0x31/0x60
kernel:  [<c03c17e9>] netlink_sendmsg+0x259/0x310
kernel:  [<c039e87b>] sock_sendmsg+0xbb/0xe0
kernel:  [<c03a0424>] sys_sendmsg+0x1c4/0x230
kernel:  [<c03a08cc>] sys_socketcall+0x21c/0x240
kernel:  [<c01029f3>] syscall_call+0x7/0xb
kernel: BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
kernel: caller is get_next_corpse+0x23f/0x260
kernel:  [<c010385e>] dump_stack+0x1e/0x30
kernel:  [<c024f13f>] smp_processor_id+0xaf/0xc0
kernel:  [<c0407faf>] get_next_corpse+0x23f/0x260
kernel:  [<c0408006>] ip_ct_iterate_cleanup+0x36/0xc0
kernel:  [<c041896a>] masq_inet_event+0x3a/0x70
kernel:  [<c012eded>] notifier_call_chain+0x2d/0x50
kernel:  [<c03ef589>] inet_del_ifa+0x99/0x150
kernel:  [<c03efafb>] inet_rtm_deladdr+0x12b/0x170
Quoted 11 lines
kernel:  [<c03b1f47>] rtnetlink_rcv+0x347/0x410
kernel:  [<c03c1b10>] netlink_data_ready+0x60/0x70
kernel:  [<c03c0f71>] netlink_sendskb+0x31/0x60
kernel:  [<c03c17e9>] netlink_sendmsg+0x259/0x310
kernel:  [<c039e87b>] sock_sendmsg+0xbb/0xe0
kernel:  [<c03a0424>] sys_sendmsg+0x1c4/0x230
kernel:  [<c03a08cc>] sys_socketcall+0x21c/0x240
kernel:  [<c01029f3>] syscall_call+0x7/0xb

Hi!
You have to use get_cpu() or __smp_processor_id() to avoid this debug message. Have a look at inlcude/linux/smp.h and include/asm-i386/smp.h.

Matthias-Christian Ott

#2 lore raw

repost: 2.6.11-rc4 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840

In reply to Frank van Maarseveen
Quoted 3 lines · Frank van Maarseveen

While executing
iptables -t nat -D OUTPUT -d 80.126.170.174 -p tcp --dport https -j DNAT --to 192.168.0.1 iptables -t nat -D OUTPUT -d 80.126.170.174 -p tcp --dport http -j DNAT --to 192.168.0.1

still present in -rc4:

kernel: BUG: using smp_processor_id() in preemptible [00000001] code: ip/6351
kernel: caller is get_next_corpse+0x13/0x260
kernel:  [<c010385e>] dump_stack+0x1e/0x30
kernel:  [<c024f60f>] smp_processor_id+0xaf/0xc0
kernel:  [<c0408c03>] get_next_corpse+0x13/0x260
kernel:  [<c0408e86>] ip_ct_iterate_cleanup+0x36/0xc0
kernel:  [<c041981a>] masq_inet_event+0x3a/0x70
kernel:  [<c012ee4d>] notifier_call_chain+0x2d/0x50
kernel:  [<c03f02d9>] inet_del_ifa+0x99/0x150
kernel:  [<c03f084b>] inet_rtm_deladdr+0x12b/0x170
kernel:  [<c03b290b>] rtnetlink_rcv+0x35b/0x420
kernel:  [<c03c26c0>] netlink_data_ready+0x60/0x70
kernel:  [<c03c1ad1>] netlink_sendskb+0x31/0x60
kernel:  [<c03c2391>] netlink_sendmsg+0x261/0x320
kernel:  [<c039f16b>] sock_sendmsg+0xbb/0xe0
kernel:  [<c03a0d14>] sys_sendmsg+0x1c4/0x230
kernel:  [<c03a11bc>] sys_socketcall+0x21c/0x240
kernel:  [<c01029f3>] syscall_call+0x7/0xb
kernel: BUG: using smp_processor_id() in preemptible [00000001] code: ip/6351
kernel: caller is get_next_corpse+0x23f/0x260
kernel:  [<c010385e>] dump_stack+0x1e/0x30
kernel:  [<c024f60f>] smp_processor_id+0xaf/0xc0
kernel:  [<c0408e2f>] get_next_corpse+0x23f/0x260
kernel:  [<c0408e86>] ip_ct_iterate_cleanup+0x36/0xc0
kernel:  [<c041981a>] masq_inet_event+0x3a/0x70
kernel:  [<c012ee4d>] notifier_call_chain+0x2d/0x50
kernel:  [<c03f02d9>] inet_del_ifa+0x99/0x150
kernel:  [<c03f084b>] inet_rtm_deladdr+0x12b/0x170
kernel:  [<c03b290b>] rtnetlink_rcv+0x35b/0x420
kernel:  [<c03c26c0>] netlink_data_ready+0x60/0x70
kernel:  [<c03c1ad1>] netlink_sendskb+0x31/0x60
kernel:  [<c03c2391>] netlink_sendmsg+0x261/0x320
kernel:  [<c039f16b>] sock_sendmsg+0xbb/0xe0
kernel:  [<c03a0d14>] sys_sendmsg+0x1c4/0x230
kernel:  [<c03a11bc>] sys_socketcall+0x21c/0x240
kernel:  [<c01029f3>] syscall_call+0x7/0xb
Signature · 1 line
Frank
#3 lore raw

Re: repost: 2.6.11-rc4 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840

Quoted 38 lines · Frank van Maarseveen
Quoted 5 lines · Frank van Maarseveen

While executing
iptables -t nat -D OUTPUT -d 80.126.170.174 -p tcp --dport https -j DNAT --to 192.168.0.1 iptables -t nat -D OUTPUT -d 80.126.170.174 -p tcp --dport http -j DNAT --to 192.168.0.1

still present in -rc4:

kernel: BUG: using smp_processor_id() in preemptible [00000001] code: ip/6351
kernel: caller is get_next_corpse+0x13/0x260
kernel:  [<c010385e>] dump_stack+0x1e/0x30
kernel:  [<c024f60f>] smp_processor_id+0xaf/0xc0
kernel:  [<c0408c03>] get_next_corpse+0x13/0x260
kernel:  [<c0408e86>] ip_ct_iterate_cleanup+0x36/0xc0
kernel:  [<c041981a>] masq_inet_event+0x3a/0x70
kernel:  [<c012ee4d>] notifier_call_chain+0x2d/0x50
kernel:  [<c03f02d9>] inet_del_ifa+0x99/0x150
kernel:  [<c03f084b>] inet_rtm_deladdr+0x12b/0x170
kernel:  [<c03b290b>] rtnetlink_rcv+0x35b/0x420
kernel:  [<c03c26c0>] netlink_data_ready+0x60/0x70
kernel:  [<c03c1ad1>] netlink_sendskb+0x31/0x60
kernel:  [<c03c2391>] netlink_sendmsg+0x261/0x320
kernel:  [<c039f16b>] sock_sendmsg+0xbb/0xe0
kernel:  [<c03a0d14>] sys_sendmsg+0x1c4/0x230
kernel:  [<c03a11bc>] sys_socketcall+0x21c/0x240
kernel:  [<c01029f3>] syscall_call+0x7/0xb
kernel: BUG: using smp_processor_id() in preemptible [00000001] code: ip/6351
kernel: caller is get_next_corpse+0x23f/0x260
kernel:  [<c010385e>] dump_stack+0x1e/0x30
kernel:  [<c024f60f>] smp_processor_id+0xaf/0xc0
kernel:  [<c0408e2f>] get_next_corpse+0x23f/0x260
kernel:  [<c0408e86>] ip_ct_iterate_cleanup+0x36/0xc0
kernel:  [<c041981a>] masq_inet_event+0x3a/0x70
kernel:  [<c012ee4d>] notifier_call_chain+0x2d/0x50
kernel:  [<c03f02d9>] inet_del_ifa+0x99/0x150
kernel:  [<c03f084b>] inet_rtm_deladdr+0x12b/0x170
Quoted 11 lines
kernel:  [<c03b290b>] rtnetlink_rcv+0x35b/0x420
kernel:  [<c03c26c0>] netlink_data_ready+0x60/0x70
kernel:  [<c03c1ad1>] netlink_sendskb+0x31/0x60
kernel:  [<c03c2391>] netlink_sendmsg+0x261/0x320
kernel:  [<c039f16b>] sock_sendmsg+0xbb/0xe0
kernel:  [<c03a0d14>] sys_sendmsg+0x1c4/0x230
kernel:  [<c03a11bc>] sys_socketcall+0x21c/0x240
kernel:  [<c01029f3>] syscall_call+0x7/0xb

Than fix it, the way I mentioned.

Matthias-Christian Ott

#4 lore raw

Re: repost: 2.6.11-rc4 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840

Quoted 2 lines · Matthias-Christian Ott
Quoted 2 lines · Frank van Maarseveen

[...]

Quoted 5 lines
Quoted 5 lines

still present in -rc4:
kernel: BUG: using smp_processor_id() in preemptible [00000001] code:
ip/6351
kernel: caller is get_next_corpse+0x13/0x260
kernel: [<c010385e>] dump_stack+0x1e/0x30

[...]

Quoted 2 lines
Quoted 1 line

Than fix it, the way I mentioned.

Yes, I can do that and thanks for the info.

I'm only reporting it because I think that it may be relevant for others:
Someone may want to fix it before 2.6.11 final comes out. I think it is easier for the maintainer and most other people on the list to notice it and fix it than it is for me to get a fix through the proper channels.

Don't worry, I won't report it a third time..

Signature · 1 line
Frank