All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Yang Shi <yang.shi@windriver.com>, ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Protect current_cpu_data with preempt disable in delay()
Date: Thu, 04 Mar 2010 10:23:47 -0800	[thread overview]
Message-ID: <4B8FFAB3.1090409@caviumnetworks.com> (raw)
In-Reply-To: <1267695573-27360-1-git-send-email-yang.shi@windriver.com>

On 03/04/2010 01:39 AM, Yang Shi wrote:
> During machine restart with reboot command, get the following
> bug info:
>
> BUG: using smp_processor_id() in preemptible [00000000] code: reboot/1989
> caller is __udelay+0x14/0x70
> Call Trace:
> [<ffffffff8110ad28>] dump_stack+0x8/0x34
> [<ffffffff812dde04>] debug_smp_processor_id+0xf4/0x110
> [<ffffffff812d90bc>] __udelay+0x14/0x70
> [<ffffffff81378274>] md_notify_reboot+0x12c/0x148
> [<ffffffff81161054>] notifier_call_chain+0x64/0xc8
> [<ffffffff811614dc>] __blocking_notifier_call_chain+0x64/0xc0
> [<ffffffff8115566c>] kernel_restart_prepare+0x1c/0x38
> [<ffffffff811556cc>] kernel_restart+0x14/0x50
> [<ffffffff8115581c>] SyS_reboot+0x10c/0x1f0
> [<ffffffff81103684>] handle_sysn32+0x44/0x84
>
> The root cause is that current_cpu_data is accessed in preemptible
> context, so protect it with preempt_disable/preempt_enable pair
> in delay().
>
> Signed-off-by: Yang Shi<yang.shi@windriver.com>
> ---
>   arch/mips/lib/delay.c |    6 +++++-
>   1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/arch/mips/lib/delay.c b/arch/mips/lib/delay.c
> index 6b3b1de..dc38064 100644
> --- a/arch/mips/lib/delay.c
> +++ b/arch/mips/lib/delay.c
> @@ -41,7 +41,11 @@ EXPORT_SYMBOL(__delay);
>
>   void __udelay(unsigned long us)
>   {
> -	unsigned int lpj = current_cpu_data.udelay_val;
> +	unsigned int lpj;
> +
> +	preempt_disable();
> +	lpj = current_cpu_data.udelay_val;
> +	preempt_enable();
>
>   	__delay((us * 0x000010c7ull * HZ * lpj)>>  32);
>   }

This doesn't seem like the best approach.

Perhaps we should either use raw_current_cpu_data and no 
preempt_disable(), or if we are concerned about migrating to a CPU with 
a different lpj value, move the preempt_enable after the call to __delay().

David Daney

  reply	other threads:[~2010-03-04 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  9:39 [PATCH] MIPS: Protect current_cpu_data with preempt disable in delay() Yang Shi
2010-03-04 18:23 ` David Daney [this message]
2010-03-05  1:10   ` Yang Shi
2010-03-08  9:42     ` Yang Shi
2010-03-10 15:33   ` Ralf Baechle
2010-03-11  3:12     ` Yang Shi

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=4B8FFAB3.1090409@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=yang.shi@windriver.com \
    /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.