From: "Alexander Beregalov" <a.beregalov@gmail.com>
To: "David Howells" <dhowells@redhat.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 19: CRED: BUG: bad unlock balance detected!
Date: Tue, 19 Aug 2008 16:36:18 +0400 [thread overview]
Message-ID: <a4423d670808190536m7896c849xaa47ab608e954cf9@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
It is sparc64 machine.
Config is attached.
[ 25.742287] [ BUG: bad unlock balance detected! ]
[ 25.750284] -------------------------------------
[ 25.758404] rc/404 is trying to release lock (&p->cred_exec_mutex) at:
[ 25.766716] [<00000000006aff78>] mutex_unlock+0x10/0x20
[ 25.775078] but there are no more locks to release!
[ 25.783548]
[ 25.783554] other info that might help us debug this:
[ 25.800205] no locks held by rc/404.
[ 25.808508]
[ 25.808514] stack backtrace:
[ 25.824764] Call Trace:
[ 25.832652] [0000000000478014] print_unlock_inbalance_bug+0xe8/0xf8
[ 25.840661] [0000000000478340] lock_release+0x98/0x1ac
[ 25.848690] [00000000006afed4] __mutex_unlock_slowpath+0xbc/0x150
[ 25.856664] [00000000006aff78] mutex_unlock+0x10/0x20
[ 25.864780] [00000000004b8460] install_exec_creds+0x1c/0x2c
[ 25.872784] [00000000004f077c] load_elf_binary+0xc98/0x11e4
[ 25.880858] [00000000004b8314] search_binary_handler+0xcc/0x1fc
[ 25.888817] [00000000004e7a18] compat_do_execve+0x178/0x1e4
[ 25.896913] [0000000000441f08] sparc32_execve+0x70/0xbc
[ 25.904811] [0000000000406154] linux_sparc_syscall32+0x34/0x40
[-- Attachment #2: config-0819-cred.gz --]
[-- Type: application/x-gzip, Size: 6609 bytes --]
next reply other threads:[~2008-08-19 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 12:36 Alexander Beregalov [this message]
2008-08-19 15:23 ` David Howells
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=a4423d670808190536m7896c849xaa47ab608e954cf9@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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®