From: Andrew Morton <akpm@osdl.org>
To: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Cc: linux-kernel@vger.kernel.org, Matt Helsley <matthltc@us.ibm.com>
Subject: Re: [BUG linux-2.6.15-rc] process events connector - soft lockup detected
Date: Fri, 25 Nov 2005 11:47:41 -0800 [thread overview]
Message-ID: <20051125114741.6549ef3a.akpm@osdl.org> (raw)
In-Reply-To: <20051125144226.37778246@frecb000711.frec.bull.fr>
Guillaume Thouvenin <guillaume.thouvenin@bull.net> wrote:
>
> Hello,
>
> I compiled a kernel 2.6.15-rc1 and a 2.6.15-rc2 with Process Events
> Connector enabled. The machine has two processors. When I use the
> process events connector, a soft lockup is detected (for both releases):
>
> ---------B<---------------------------------------
> Pid: 2770, comm: sh
> EIP: 0060:[<c039ae28>] CPU: 1
> EIP is at __read_lock_failed+0x8/0x14
> EFLAGS: 00000297 Not tainted (2.6.15-rc2)
> EAX: c046fc00 EBX: f5946000 ECX: f5947f7c EDX: 00000286
> ESI: 00000000 EDI: ffffffff EBP: f5946000 DS: 007b ES: 007b
> CR0: 8005003b CR2: 080e173c CR3: 358a0000 CR4: 000006d0
> [<c039c566>] _read_lock+0xb/0xc
> [<c011e7ee>] do_wait+0x9d/0x40c
> [<c0116fd0>] default_wake_function+0x0/0x12
> [<c0116fd0>] default_wake_function+0x0/0x12
> [<c011ec32>] sys_wait4+0x43/0x45
> [<c0102e39>] syscall_call+0x7/0xb
> BUG: soft lockup detected on CPU#1!
>
> ...
>
> I think that the problem is in kernel/fork.c. The function
> proc_fork_connector(p) is called inside a
> write_lock_irq(&tasklist_lock). The
> cn_netlink_send(msg,CN_IDX_PROC,GFP_KERNEL) is called by the
> proc_fork_connector(). Thus, the alloc_skb(size,GFP_KERNEL) is called
> within a write_lock_irq(&tasklist_lock)... is it the problem?
>
> If I replace GFP_KERNEL by GFP_ATOMIC the soft lockup disappear (but I
> don't know if this solution is right...)
Gad, how ddd that get in there?
--- devel/kernel/fork.c~forkc-proc_fork_connector-called-under-write_lock 2005-11-25 11:46:36.000000000 -0800
+++ devel-akpm/kernel/fork.c 2005-11-25 11:46:36.000000000 -0800
@@ -1135,13 +1135,13 @@ static task_t *copy_process(unsigned lon
__get_cpu_var(process_counts)++;
}
- proc_fork_connector(p);
if (!current->signal->tty && p->signal->tty)
p->signal->tty = NULL;
nr_threads++;
total_forks++;
write_unlock_irq(&tasklist_lock);
+ proc_fork_connector(p);
retval = 0;
fork_out:
_
next prev parent reply other threads:[~2005-11-25 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 13:42 [BUG linux-2.6.15-rc] process events connector - soft lockup detected Guillaume Thouvenin
2005-11-25 19:47 ` Andrew Morton [this message]
2005-11-25 19:57 ` Andrew Morton
2005-11-25 22:29 ` Paul Jackson
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=20051125114741.6549ef3a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=guillaume.thouvenin@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
/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