From: "Paul Rolland" <rol@witbe.net>
To: linux-kernel@vger.kernel.org
Cc: "Paul Rolland" <rol@witbe.net>
Subject: Re: Blocked in keyctl(...) ??? - RCU related ???
Date: Fri, 16 Mar 2012 09:43:28 +0100 [thread overview]
Message-ID: <20120316094328.6b37a4d9@tux.DEF.witbe.net> (raw)
In-Reply-To: <20120312170301.5982e054@tux.DEF.witbe.net>
[-- Attachment #1.1: Type: text/plain, Size: 2133 bytes --]
Hello,
On Mon, 12 Mar 2012 17:03:01 +0100
Paul Rolland (ポール・ロラン) <rol@witbe.net> wrote:
> Sometimes, my applications start "locking": nothing happens anymore, can't
> kill them...
> I manage to strace them, to find that they are executing the following
> syscall:
>
> 13686 keyctl(0x1, 0, 0xffffffffffffffff, 0x7fa90fd6a2c0, 0
>
> and that syscall never returns.
OK, this happened again, while running 3.3-rc7... I've used sysrq to
collect some informations and what I can see from that is the following :
Mar 16 08:40:02 tux kernel: Call Trace:
Mar 16 08:40:02 tux kernel: [<ffffffff813b8771>] ? extract_buf+0x91/0x140
Mar 16 08:40:02 tux kernel: [<ffffffff8166fd5a>] schedule+0x3a/0x50
Mar 16 08:40:02 tux kernel: [<ffffffff8166e09d>] schedule_timeout+0x1ed/0x260
Mar 16 08:40:02 tux kernel: [<ffffffff810636c1>] ? get_parent_ip+0x11/0x50
Mar 16 08:40:02 tux kernel: [<ffffffff810636c1>] ? get_parent_ip+0x11/0x50
Mar 16 08:40:02 tux kernel: [<ffffffff810636c1>] ? get_parent_ip+0x11/0x50
Mar 16 08:40:02 tux kernel: [<ffffffff8166f100>] wait_for_common+0xc0/0x160
Mar 16 08:40:02 tux kernel: [<ffffffff81062150>] ? try_to_wake_up+0x2e0/0x2e0
Mar 16 08:40:02 tux kernel: [<ffffffff810ad020>] ? __call_rcu+0x150/0x150
Mar 16 08:40:02 tux kernel: [<ffffffff8166f1b8>] wait_for_completion+0x18/0x20
Mar 16 08:40:02 tux kernel: [<ffffffff81054628>] wait_rcu_gp+0x48/0x50
Mar 16 08:40:02 tux kernel: [<ffffffff81054630>] ? wait_rcu_gp+0x50/0x50
Mar 16 08:40:02 tux kernel: [<ffffffff810ac09c>] synchronize_rcu+0x1c/0x20
Mar 16 08:40:02 tux kernel: [<ffffffff812ba6a9>] install_session_keyring_to_cred+0x59/0xc0
Mar 16 08:40:02 tux kernel: [<ffffffff812bac3a>] join_session_keyring+0x12a/0x170
Mar 16 08:40:02 tux kernel: [<ffffffff812b8cd2>] keyctl_join_session_keyring+0x32/0x60
Mar 16 08:40:02 tux kernel: [<ffffffff812ba278>] sys_keyctl+0x168/0x180
Mar 16 08:40:02 tux kernel: [<ffffffff81671b62>]
system_call_fastpath+0x16/0x1b
The complete traces collected in /var/log/messages is attached to this email.
Is there anything I can do to investigate this ?
Paul
[-- Attachment #1.2: messages.gz --]
[-- Type: application/x-gzip, Size: 24086 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-16 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 16:03 Blocked in keyctl(...) ??? Paul Rolland
2012-03-16 8:43 ` Paul Rolland [this message]
2012-04-01 3:02 ` Blocked in keyctl(...) ??? - RCU related ??? Paul E. McKenney
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=20120316094328.6b37a4d9@tux.DEF.witbe.net \
--to=rol@witbe.net \
--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 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®