From: Sergey Senozhatsky <sergey.senozhatsky@mail.by>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kmemeleak BUG: lock held when returning to user space!
Date: Thu, 9 Jul 2009 13:55:49 +0300 [thread overview]
Message-ID: <20090709105549.GB3434@localdomain.by> (raw)
In-Reply-To: <tnxeisquo90.fsf@pc1117.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On (07/09/09 11:47), Catalin Marinas wrote:
> Date: Thu, 09 Jul 2009 11:47:23 +0100
> From: Catalin Marinas <catalin.marinas@arm.com>
> To: Sergey Senozhatsky <sergey.senozhatsky@mail.by>
> Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
> linux-kernel@vger.kernel.org, linux-mm@kvack.org
> Subject: Re: kmemeleak BUG: lock held when returning to user space!
> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
>
> Sergey Senozhatsky <sergey.senozhatsky@mail.by> wrote:
> > kernel: [ 149.507103] ================================================
> > kernel: [ 149.507113] [ BUG: lock held when returning to user space! ]
> > kernel: [ 149.507119] ------------------------------------------------
> > kernel: [ 149.507127] cat/3279 is leaving the kernel with locks still held!
> > kernel: [ 149.507135] 1 lock held by cat/3279:
> > kernel: [ 149.507141] #0: (scan_mutex){+.+.+.}, at: [<c110707c>] kmemleak_open+0x4c/0x80
> >
> > problem is here:
> > static int kmemleak_open(struct inode *inode, struct file *file)
>
> It's been fixed in my kmemleak branch which I'll push to Linus:
>
Ok. Nice to hear.
> http://www.linux-arm.org/git?p=linux-2.6.git;a=shortlog;h=kmemleak
>
> --
> Catalin
>
Sergey
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 315 bytes --]
prev parent reply other threads:[~2009-07-09 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 10:42 Sergey Senozhatsky
2009-07-09 10:47 ` Catalin Marinas
2009-07-09 10:55 ` Sergey Senozhatsky [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=20090709105549.GB3434@localdomain.by \
--to=sergey.senozhatsky@mail.by \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
/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