From: Matthias-Christian Ott <matthias.christian@tiscali.de>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: repost: 2.6.11-rc4 BUG: using smp_processor_id() in preemptible [00000001] code: ip/6840
Date: Mon, 14 Feb 2005 15:03:49 +0100 [thread overview]
Message-ID: <4210AFC5.2030807@tiscali.de> (raw)
In-Reply-To: <20050213193037.GA2802@janus>
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
next prev parent reply other threads:[~2005-02-14 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2005-02-14 14:18 ` Frank van Maarseveen
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=4210AFC5.2030807@tiscali.de \
--to=matthias.christian@tiscali.de \
--cc=frankvm@frankvm.com \
--cc=linux-kernel@vger.kernel.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 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.