* 2.6.11-rc3 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
@ 2005-02-06 19:51 Frank van Maarseveen
2005-02-06 20:05 ` Matthias-Christian Ott
2005-02-13 19:30 ` repost: 2.6.11-rc4 " Frank van Maarseveen
0 siblings, 2 replies; 5+ messages in thread
From: Frank van Maarseveen @ 2005-02-06 19:51 UTC (permalink / raw)
To: linux-kernel
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
--
Frank
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6.11-rc3 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
2005-02-06 19:51 2.6.11-rc3 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840 Frank van Maarseveen
@ 2005-02-06 20:05 ` Matthias-Christian Ott
2005-02-13 19:30 ` repost: 2.6.11-rc4 " Frank van Maarseveen
1 sibling, 0 replies; 5+ messages in thread
From: Matthias-Christian Ott @ 2005-02-06 20:05 UTC (permalink / raw)
To: Frank van Maarseveen; +Cc: linux-kernel
Frank van Maarseveen wrote:
>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
>
>
>
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* repost: 2.6.11-rc4 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
2005-02-06 19:51 2.6.11-rc3 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840 Frank van Maarseveen
2005-02-06 20:05 ` Matthias-Christian Ott
@ 2005-02-13 19:30 ` Frank van Maarseveen
2005-02-14 14:03 ` Matthias-Christian Ott
1 sibling, 1 reply; 5+ messages in thread
From: Frank van Maarseveen @ 2005-02-13 19:30 UTC (permalink / raw)
To: linux-kernel
On Sun, Feb 06, 2005 at 08:51:11PM +0100, Frank van Maarseveen wrote:
> 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
--
Frank
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: repost: 2.6.11-rc4 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
2005-02-13 19:30 ` repost: 2.6.11-rc4 " Frank van Maarseveen
@ 2005-02-14 14:03 ` Matthias-Christian Ott
2005-02-14 14:18 ` Frank van Maarseveen
0 siblings, 1 reply; 5+ messages in thread
From: Matthias-Christian Ott @ 2005-02-14 14:03 UTC (permalink / raw)
To: Frank van Maarseveen; +Cc: linux-kernel
Frank van Maarseveen wrote:
>On Sun, Feb 06, 2005 at 08:51:11PM +0100, Frank van Maarseveen wrote:
>
>
>>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
>
>
>
Than fix it, the way I mentioned.
Matthias-Christian Ott
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: repost: 2.6.11-rc4 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
2005-02-14 14:03 ` Matthias-Christian Ott
@ 2005-02-14 14:18 ` Frank van Maarseveen
0 siblings, 0 replies; 5+ messages in thread
From: Frank van Maarseveen @ 2005-02-14 14:18 UTC (permalink / raw)
To: Matthias-Christian Ott; +Cc: linux-kernel
On Mon, Feb 14, 2005 at 03:03:49PM +0100, Matthias-Christian Ott wrote:
> >On Sun, Feb 06, 2005 at 08:51:11PM +0100, Frank van Maarseveen wrote:
> >
[...]
> >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
[...]
> >
> 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..
--
Frank
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2005-02-14 14:18 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-06 19:51 2.6.11-rc3 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840 Frank van Maarseveen
2005-02-06 20:05 ` Matthias-Christian Ott
2005-02-13 19:30 ` repost: 2.6.11-rc4 " Frank van Maarseveen
2005-02-14 14:03 ` Matthias-Christian Ott
2005-02-14 14:18 ` Frank van Maarseveen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox