From: Luming Yu <luming.yu@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Luck, Tony" <tony.luck@intel.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: ia64 lockdep: trying to register non-static key (mm->mmap_sem)
Date: Thu, 26 Nov 2009 13:52:13 +0800 [thread overview]
Message-ID: <3877989d0911252152g6bd13a32oc387e282eceda3f1@mail.gmail.com> (raw)
In-Reply-To: <3877989d0911251943j6860e88ci93e237ba65835bc7@mail.gmail.com>
sorry for noise, I've figured it out that locdep annoatation is missed in IA64
__rwsem_initializer.
On Thu, Nov 26, 2009 at 11:43 AM, Luming Yu <luming.yu@gmail.com> wrote:
> Anybody know how I should do to fix the lockdep
> warning below, which is triggered in
> ia64_brk doing "down_write(&mm->mmap_sem)"
>
> Any comments are appreciated.
>
>
> INFO: trying to register non-static key.
> the code is fine but needs lockdep annotation.
> turning off the locking correctness validator.
>
> Call Trace:
> [<a000000100017330>] show_stack+0x70/0xc0
> sp=e0000004807a7c50 bsp=e0000004807a1c78
> [<a0000001000173d0>] dump_stack+0x50/0x80
> sp=e0000004807a7e20 bsp=e0000004807a1c58
> [<a0000001000f7ca0>] __lock_acquire+0x1a0/0x13e0
> sp=e0000004807a7e20 bsp=e0000004807a1bc0
> [<a0000001000fc310>] lock_acquire+0x170/0x1e0
> sp=e0000004807a7e20 bsp=e0000004807a1b60
> [<a0000001008338d0>] down_write+0x70/0x180
> sp=e0000004807a7e20 bsp=e0000004807a1b28
> [<a00000010003b960>] ia64_brk+0x60/0x280
> sp=e0000004807a7e20 bsp=e0000004807a1aa0
> [<a00000010000c620>] ia64_ret_from_syscall+0x0/0x20
>
>
> Thanks,
> Luming
>
prev parent reply other threads:[~2009-11-26 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 3:43 Luming Yu
2009-11-26 5:52 ` Luming Yu [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=3877989d0911252152g6bd13a32oc387e282eceda3f1@mail.gmail.com \
--to=luming.yu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®