From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: fix "BUG: using smp_processor_id() in preemptible code"
Date: Fri, 1 Jan 2010 20:35:44 +0000 [thread overview]
Message-ID: <20100101203544.GG16220@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1262193440-17794-1-git-send-email-rabin@rab.in>
On Wed, Dec 30, 2009 at 10:47:20PM +0530, Rabin Vincent wrote:
> Fix the following warning, which appears when the register dump for a
> faulting process is printed in a kernel with SMP, DEBUG_PREEMPT, and
> DEBUG_USER (with user_debug=31) enabled:
Well, the CPU number displayed here in preemptible contexts is rather
meaningless - it doesn't necessarily reflect the CPU where the problem
originally occurred.
Maybe we should use raw_smp_processor_id() here - which is fine because
this is just debugging, and it being wrong doesn't cause unsafe
conditions.
next prev parent reply other threads:[~2010-01-01 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 17:17 [PATCH] ARM: fix "BUG: using smp_processor_id() in preemptible code" Rabin Vincent
2010-01-01 20:35 ` Russell King - ARM Linux [this message]
2010-01-04 14:50 ` Rabin Vincent
-- strict thread matches above, loose matches on Subject: below --
2009-12-30 16:58 Rabin Vincent
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=20100101203544.GG16220@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).