From: Patrick McHardy <kaber@trash.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Harald Welte <laforge@netfilter.org>
Subject: Re: 2.6.13-rc5-mm1: BUG: rwlock recursion on CPU#0
Date: Sun, 14 Aug 2005 15:18:48 +0200 [thread overview]
Message-ID: <42FF44B8.9000007@trash.net> (raw)
In-Reply-To: <200508141448.36562.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> I've got the following BUG on Asus L5D (x86-64) with the 2.6.13-rc5-mm1 kernel:
>
> BUG: rwlock recursion on CPU#0, nscd/3668, ffffffff8817d4a0
>
> Call Trace:<ffffffff80241ca9>{add_preempt_count+105} <ffffffff80241682>{rwlock_bug+114}
> <ffffffff8024179e>{_raw_write_lock+62} <ffffffff80350f48>{_write_lock_bh+40}
> <ffffffff88171824>{:ip_conntrack:destroy_conntrack+196}
> <ffffffff88170435>{:ip_conntrack:__ip_ct_event_cache_init+165}
> <ffffffff88170549>{:ip_conntrack:ip_ct_refresh_acct+249}
> <ffffffff88173c4f>{:ip_conntrack:udp_packet+47} <ffffffff88172143>{:ip_conntrack:ip_conntrack_in+1059}
> <ffffffff8816fb4c>{:ip_conntrack:ip_conntrack_local+76}
> <ffffffff802fe7ec>{nf_iterate+92} <ffffffff80311d90>{dst_output+0}
> <ffffffff802ff3de>{nf_hook_slow+142} <ffffffff80311d90>{dst_output+0}
> <ffffffff803123bf>{ip_push_pending_frames+895} <ffffffff802eade9>{lock_sock+201}
> <ffffffff8032e72e>{udp_push_pending_frames+574} <ffffffff8032ffc7>{udp_sendmsg+1703}
> <ffffffff8013874e>{current_fs_time+78} <ffffffff8015c03c>{file_read_actor+60}
> <ffffffff80199b6c>{update_atime+76} <ffffffff8015e8fa>{do_generic_mapping_read+1194}
> <ffffffff80335946>{inet_sendmsg+86} <ffffffff802e7dff>{sock_sendmsg+271}
> <ffffffff80241ca9>{add_preempt_count+105} <ffffffff8016153e>{free_hot_cold_page+270}
> <ffffffff801615bb>{free_hot_page+11} <ffffffff80241ca9>{add_preempt_count+105}
> <ffffffff8014a670>{autoremove_wake_function+0} <ffffffff802e846c>{sockfd_lookup+28}
> <ffffffff802e9c64>{sys_sendto+260} <ffffffff80193003>{do_sys_poll+851}
> <ffffffff80193de0>{__pollwait+0} <ffffffff8010eb3e>{system_call+126}
I fear my event cache fixes are responsible for this, we must not cache
events while holding a lock anymore because we might need to deliver
old cached events. I'll try to come up with a fix later.
next prev parent reply other threads:[~2005-08-14 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 12:48 2.6.13-rc5-mm1: BUG: rwlock recursion on CPU#0 Rafael J. Wysocki
2005-08-14 13:18 ` Patrick McHardy [this message]
2005-08-15 2:15 ` Zwane Mwaikambo
2005-08-15 9:37 ` Harald Welte
2005-08-15 14:25 ` Zwane Mwaikambo
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=42FF44B8.9000007@trash.net \
--to=kaber@trash.net \
--cc=akpm@osdl.org \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rjw@sisk.pl \
/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