From: Ben Greear <greearb@candelatech.com>
To: netdev <netdev@vger.kernel.org>
Subject: Re: Locking bug in 3.0.25, IPv6.
Date: Mon, 26 Mar 2012 11:41:52 -0700 [thread overview]
Message-ID: <4F70B870.4090900@candelatech.com> (raw)
In-Reply-To: <4F709EAA.6040700@candelatech.com>
On 03/26/2012 09:51 AM, Ben Greear wrote:
> Has anyone seen this in 3.0.25? My kernel has some other patches
> applied, but we did not see this before 3.0.24.
>
> BUG: sleeping function called from invalid context at /home/greearb/git/linux-3.0.dev.y/mm/memory.c:3904
Just FYI: This happens in un-modified kernels...seems to have been introduced
(or made more visible) somewhere between 3.0.19 and 3.0.23.
I'm bisecting it now...
Thanks,
Ben
>
> ================================================
> [ BUG: lock held when returning to user space! ]
> ------------------------------------------------
> ip/6696 is leaving the kernel with locks still held!
> 1 lock held by ip/6696:
> #0: (rcu_read_lock){.+.+..}, at: [<ffffffffa03051c4>] rcu_read_lock+0x0/0x35 [ipv6]
> in_atomic(): 0, irqs_disabled(): 0, pid: 6694, name: ip
> INFO: lockdep is turned off.
> Pid: 6694, comm: ip Tainted: G C 3.0.25+ #1
> Call Trace:
> [<ffffffff8103e479>] __might_sleep+0x111/0x115
> [<ffffffff810c98bf>] might_fault+0x2f/0x9e
> [<ffffffff8138698e>] ? copy_from_user+0x2a/0x2c
> [<ffffffff810c98de>] ? might_fault+0x4e/0x9e
> [<ffffffff8137cc90>] move_addr_to_user+0x21/0x8e
> [<ffffffff8137ce7c>] __sys_recvmsg+0x17f/0x21e
> [<ffffffff810634a8>] ? up_read+0x1e/0x36
> [<ffffffff810fc06e>] ? fcheck_files+0xb7/0xee
> [<ffffffff810fc191>] ? fget_light+0x35/0xac
> [<ffffffff810d0023>] ? remove_vma+0x7a/0x82
> [<ffffffff8137d620>] sys_recvmsg+0x3d/0x5b
> [<ffffffff8144f092>] system_call_fastpath+0x16/0x1b
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-03-26 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 16:51 Locking bug in 3.0.25, IPv6 Ben Greear
2012-03-26 18:41 ` Ben Greear [this message]
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=4F70B870.4090900@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@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.