From: Gautham R Shenoy <ego@in.ibm.com>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug() - 2.6.18.6
Date: Fri, 16 Feb 2007 10:48:23 +0530 [thread overview]
Message-ID: <20070216051823.GA9195@in.ibm.com> (raw)
In-Reply-To: <45D4C999.4080507@nagafix.co.uk>
Hi Antoine,
On Thu, Feb 15, 2007 at 08:59:05PM +0000, Antoine Martin wrote:
> I just caught this in the log whilst running some unit tests.
> (the test was in the process of starting 900 Java threads)
>
> audit(1171565587.887:96): enforcing=0 old_enforcing=1 auid=4294967295
> BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug()
>
> Call Trace:
> [<ffffffff80269c98>] dump_stack+0x12/0x17
> [<ffffffff8029dfe6>] unlock_cpu_hotplug+0x3f/0x6c
> [<ffffffff802876b6>] sched_getaffinity+0x7d/0xa2
> [<ffffffff80287701>] sys_sched_getaffinity+0x26/0x55
> [<ffffffff8025cb0e>] system_call+0x7e/0x83
Looks like one of those spurious unlock_cpu_hotplug warnings.
Let me know if this fix works for you or not.
regards
gautham.
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
kernel/cpu.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.18/kernel/cpu.c
===================================================================
--- linux-2.6.18.orig/kernel/cpu.c
+++ linux-2.6.18/kernel/cpu.c
@@ -53,8 +53,8 @@ void unlock_cpu_hotplug(void)
recursive_depth--;
return;
}
- mutex_unlock(&cpu_bitmask_lock);
recursive = NULL;
+ mutex_unlock(&cpu_bitmask_lock);
}
EXPORT_SYMBOL_GPL(unlock_cpu_hotplug);
--
Gautham R Shenoy
Linux Technology Center
IBM India.
"Freedom comes with a price tag of responsibility, which is still a bargain,
because Freedom is priceless!"
prev parent reply other threads:[~2007-02-16 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 20:59 BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug() - 2.6.18.6 Antoine Martin
2007-02-16 5:18 ` Gautham R Shenoy [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=20070216051823.GA9195@in.ibm.com \
--to=ego@in.ibm.com \
--cc=antoine@nagafix.co.uk \
--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