From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [BUG] Error in copy_process, when enable CONFIG_PROVE_LOCKING.
Date: Wed, 29 Jul 2009 14:11:16 +0000 [thread overview]
Message-ID: <20090729141116.GA24109@linux-sh.org> (raw)
In-Reply-To: <29ab51dc0905112140v3187b462qcc8a9e5385de8ef6@mail.gmail.com>
On Tue, May 12, 2009 at 01:40:35PM +0900, Nobuhiro Iwamatsu wrote:
> Error in copy_process, when enable CONFIG_PROVE_LOCKING.
> This error has p->hardirqs_enabled in kernel.fork.c
>
> 987 #ifdef CONFIG_PROVE_LOCKING
> 988 DEBUG_LOCKS_WARN_ON(!p->hardirqs_enabled);
> 989 DEBUG_LOCKS_WARN_ON(!p->softirqs_enabled);
> 990 #endif
> 991 retval = -EAGAIN;
>
> The error message is as follows.
> I am debuging this. Please teach if you know the revision method of
> this problem.
>
This should be fixed now in current git. Can you give it a try?
next prev parent reply other threads:[~2009-07-29 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 4:40 [BUG] Error in copy_process, when enable CONFIG_PROVE_LOCKING Nobuhiro Iwamatsu
2009-05-12 12:15 ` Stuart MENEFY
2009-05-18 4:11 ` Paul Mundt
2009-05-18 17:18 ` Stuart MENEFY
2009-07-29 14:11 ` Paul Mundt [this message]
2009-08-19 6:35 ` Nobuhiro Iwamatsu
2009-09-04 8:15 ` Nobuhiro Iwamatsu
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=20090729141116.GA24109@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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.