From: David Howells <dhowells@redhat.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: dhowells@redhat.com, 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:23:18 +0100 [thread overview]
Message-ID: <24643.1219159398@redhat.com> (raw)
In-Reply-To: <a4423d670808190536m7896c849xaa47ab608e954cf9@mail.gmail.com>
Alexander Beregalov <a.beregalov@gmail.com> wrote:
> [ 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!
I forgot to lock cred_exec_mutex in compat_do_execve(). I've posted a patch
which should fix this:
Subject: [PATCH] CRED: Take cred_exec_mutex in compat_do_execve() and fix
error handling in do_execve()
David
prev parent reply other threads:[~2008-08-19 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 12:36 linux-next: Tree for August 19: CRED: BUG: bad unlock balance detected! Alexander Beregalov
2008-08-19 15:23 ` David Howells [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=24643.1219159398@redhat.com \
--to=dhowells@redhat.com \
--cc=a.beregalov@gmail.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 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.