mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Yinghai Lu <yinghai@kernel.org>,
	Naga Chumbalkar <nagananda.chumbalkar@hp.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: check for valid irq_cfg pointer in smp_irq_move_cleanup_interrupt
Date: Mon, 21 May 2012 14:05:53 -0700	[thread overview]
Message-ID: <1337634353.1997.144.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <20120521164959.GE16454@sgi.com>

On Mon, 2012-05-21 at 11:49 -0500, Dimitri Sivanich wrote:
> The smp_irq_move_cleanup_interrupt routine should be checking for a valid
> irq_cfg pointer prior to accessing it.  It also seems that this should be
> done after taking the desc lock.

I think these changes are correct. Did you see any crashes during module
unload etc?

Reviewed-by: Suresh Siddha <suresh.b.siddha@intel.com>

> 
> Signed-off-by: Dimitri Sivanich <sivanich@sgi.com>
> ---
>  arch/x86/kernel/apic/io_apic.c |    5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> Index: linux/arch/x86/kernel/apic/io_apic.c
> ===================================================================
> --- linux.orig/arch/x86/kernel/apic/io_apic.c
> +++ linux/arch/x86/kernel/apic/io_apic.c
> @@ -2478,9 +2478,12 @@ asmlinkage void smp_irq_move_cleanup_int
>  		if (!desc)
>  			continue;
>  
> -		cfg = irq_cfg(irq);
>  		raw_spin_lock(&desc->lock);
>  
> +		cfg = irq_cfg(irq);
> +		if (!cfg)
> +			goto unlock;
> +
>  		/*
>  		 * Check if the irq migration is in progress. If so, we
>  		 * haven't received the cleanup request yet for this irq.



  reply	other threads:[~2012-05-21 21:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 16:49 Dimitri Sivanich
2012-05-21 21:05 ` Suresh Siddha [this message]
2012-05-21 21:09   ` Dimitri Sivanich
2012-05-21 21:10     ` Suresh Siddha
2012-05-22  2:41       ` Dimitri Sivanich
2012-05-21 21:07 ` Thomas Gleixner
2012-05-21 21:19   ` Dimitri Sivanich
2012-05-21 21:34     ` Thomas Gleixner
2012-05-23 18:16       ` Dimitri Sivanich
2012-05-23 19:04         ` Dimitri Sivanich
2012-05-23 19:24           ` Thomas Gleixner
2012-05-23 19:24           ` Suresh Siddha
2012-05-23 20:02             ` Dimitri Sivanich
2012-05-23 23:49               ` Suresh Siddha
2012-05-24  1:40                 ` Dimitri Sivanich
2012-05-24 14:37                 ` Dimitri Sivanich
2012-05-24 18:19                   ` Suresh Siddha
2012-05-24 19:16                     ` Thomas Gleixner
2012-05-26  0:23                       ` Suresh Siddha
2012-05-26 10:18                         ` Thomas Gleixner
2012-05-27  1:41                           ` Jiang Liu
2012-05-30 13:46                           ` Dimitri Sivanich
2012-05-24 14:53                 ` Thomas Gleixner
2012-05-24 15:36                   ` Dimitri Sivanich
2012-10-16 12:50 Dimitri Sivanich

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=1337634353.1997.144.camel@sbsiddha-desk.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=hpa@zytor.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nagananda.chumbalkar@hp.com \
    --cc=sivanich@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yinghai@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®