mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: xilinx: Fix for call trace due to the usage of smp_processor_id()
Date: Wed, 15 Nov 2023 15:03:19 +0100	[thread overview]
Message-ID: <ae327757-11e2-44a8-8711-dcde7bdedffc@amd.com> (raw)
In-Reply-To: <20231027055622.21544-1-jay.buddhabhatti@amd.com>



On 10/27/23 07:56, Jay Buddhabhatti wrote:
> From: HariBabu Gattem <haribabu.gattem@xilinx.com>
> 
> When preemption is enabled in kernel and if any task which can be
> preempted should not use smp_processor_id() directly, since CPU
> switch can happen at any time, the previous value of cpu_id
> differs with current cpu_id. As a result we see the below call trace
> during xlnx_event_manager_probe.
> 
> [ 6.140197] dump_backtrace+0x0/0x190
> [ 6.143884] show_stack+0x18/0x40
> [ 6.147220] dump_stack_lvl+0x7c/0xa0
> [ 6.150907] dump_stack+0x18/0x34
> [ 6.154241] check_preemption_disabled+0x124/0x134
> [ 6.159068] debug_smp_processor_id+0x20/0x2c
> [ 6.163453] xlnx_event_manager_probe+0x48/0x250
> 
> To protect cpu_id, It is recommended to use get_cpu()/put_cpu()
> to disable preemption, get the cpu_id and enable preemption respectively.
> (For Reference, Documentation/locking/preempt-locking.rst and
> Documentation/kernel-hacking/hacking.rst)
> 
> Use preempt_disable()/smp_processor_id()/preempt_enable()
> API's to achieve the same.
> 
> Signed-off-by: HariBabu Gattem <haribabu.gattem@xilinx.com>
> Signed-off-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
> ---
>   drivers/soc/xilinx/xlnx_event_manager.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/soc/xilinx/xlnx_event_manager.c b/drivers/soc/xilinx/xlnx_event_manager.c
> index 86a048a10a13..edfb1d5c10c6 100644
> --- a/drivers/soc/xilinx/xlnx_event_manager.c
> +++ b/drivers/soc/xilinx/xlnx_event_manager.c
> @@ -555,7 +555,7 @@ static void xlnx_disable_percpu_irq(void *data)
>   static int xlnx_event_init_sgi(struct platform_device *pdev)
>   {
>   	int ret = 0;
> -	int cpu = smp_processor_id();
> +	int cpu;
>   	/*
>   	 * IRQ related structures are used for the following:
>   	 * for each SGI interrupt ensure its mapped by GIC IRQ domain
> @@ -592,9 +592,12 @@ static int xlnx_event_init_sgi(struct platform_device *pdev)
>   	sgi_fwspec.param[0] = sgi_num;
>   	virq_sgi = irq_create_fwspec_mapping(&sgi_fwspec);
>   
> +	cpu = get_cpu();
>   	per_cpu(cpu_number1, cpu) = cpu;
>   	ret = request_percpu_irq(virq_sgi, xlnx_event_handler, "xlnx_event_mgmt",
>   				 &cpu_number1);
> +	put_cpu();
> +
>   	WARN_ON(ret);
>   	if (ret) {
>   		irq_dispose_mapping(virq_sgi);

Applied.
M

      reply	other threads:[~2023-11-15 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  5:56 Jay Buddhabhatti
2023-11-15 14:03 ` Michal Simek [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=ae327757-11e2-44a8-8711-dcde7bdedffc@amd.com \
    --to=michal.simek@amd.com \
    --cc=jay.buddhabhatti@amd.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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

all inboxes | Powered by JetHome®