linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>,
	Philippe Bergheaud <philippe.bergheaud@fr.ibm.com>
Cc: "Alastair D'Silva" <alastair@au1.ibm.com>,
	stable@vger.kernel.org, Ian Munsie <imunsie@au1.ibm.com>,
	Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
	linuxppc-dev@lists.ozlabs.org,
	Christophe Lombard <christophe_lombard@fr.ibm.com>,
	Greg Kurz <gkurz@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] cxl: Avoid double free_irq() for psl,slice interrupts
Date: Tue, 6 Jun 2017 10:09:31 +0200	[thread overview]
Message-ID: <4feb3b9f-d9a6-d6ae-ffff-d96c7a820b25@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170602165648.18775-1-vaibhav@linux.vnet.ibm.com>



Le 02/06/2017 à 18:56, Vaibhav Jain a écrit :
> During an eeh call to cxl_remove can result in double free_irq of
> psl,slice interrupts. This can happen if perst_reloads_same_image == 1
> and call to cxl_configure_adapter() fails during slot_reset
> callback. In such a case we see a kernel oops with following back-trace:
> 
> Oops: Kernel access of bad area, sig: 11 [#1]
> Call Trace:
>    free_irq+0x88/0xd0 (unreliable)
>    cxl_unmap_irq+0x20/0x40 [cxl]
>    cxl_native_release_psl_irq+0x78/0xd8 [cxl]
>    pci_deconfigure_afu+0xac/0x110 [cxl]
>    cxl_remove+0x104/0x210 [cxl]
>    pci_device_remove+0x6c/0x110
>    device_release_driver_internal+0x204/0x2e0
>    pci_stop_bus_device+0xa0/0xd0
>    pci_stop_and_remove_bus_device+0x28/0x40
>    pci_hp_remove_devices+0xb0/0x150
>    pci_hp_remove_devices+0x68/0x150
>    eeh_handle_normal_event+0x140/0x580
>    eeh_handle_event+0x174/0x360
>    eeh_event_handler+0x1e8/0x1f0
> 
> This patch fixes the issue of double free_irq by checking that
> variables that hold the virqs (err_hwirq, serr_hwirq, psl_virq) are
> not '0' before un-mapping and resetting these variables to '0' when
> they are un-mapped.
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
> 
> ---

Thanks for the correction.

Acked-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>

   Fred


> Changelog:
> 
> v2:
> - Use psl_hwirq instead of psl_virq to find irq mapping in
> cxl_native_release_psl_irq as pointed out by Fred.
> 
> Re-send:
> - Added stable to recipients
> ---
>   drivers/misc/cxl/native.c | 14 +++++++++++---
>   1 file changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/misc/cxl/native.c b/drivers/misc/cxl/native.c
> index 871a2f0..8d6ea97 100644
> --- a/drivers/misc/cxl/native.c
> +++ b/drivers/misc/cxl/native.c
> @@ -1302,13 +1302,16 @@ int cxl_native_register_psl_err_irq(struct cxl *adapter)
> 
>   void cxl_native_release_psl_err_irq(struct cxl *adapter)
>   {
> -	if (adapter->native->err_virq != irq_find_mapping(NULL, adapter->native->err_hwirq))
> +	if (adapter->native->err_virq == 0 ||
> +	    adapter->native->err_virq !=
> +	    irq_find_mapping(NULL, adapter->native->err_hwirq))
>   		return;
> 
>   	cxl_p1_write(adapter, CXL_PSL_ErrIVTE, 0x0000000000000000);
>   	cxl_unmap_irq(adapter->native->err_virq, adapter);
>   	cxl_ops->release_one_irq(adapter, adapter->native->err_hwirq);
>   	kfree(adapter->irq_name);
> +	adapter->native->err_virq = 0;
>   }
> 
>   int cxl_native_register_serr_irq(struct cxl_afu *afu)
> @@ -1346,13 +1349,15 @@ int cxl_native_register_serr_irq(struct cxl_afu *afu)
> 
>   void cxl_native_release_serr_irq(struct cxl_afu *afu)
>   {
> -	if (afu->serr_virq != irq_find_mapping(NULL, afu->serr_hwirq))
> +	if (afu->serr_virq == 0 ||
> +	    afu->serr_virq != irq_find_mapping(NULL, afu->serr_hwirq))
>   		return;
> 
>   	cxl_p1n_write(afu, CXL_PSL_SERR_An, 0x0000000000000000);
>   	cxl_unmap_irq(afu->serr_virq, afu);
>   	cxl_ops->release_one_irq(afu->adapter, afu->serr_hwirq);
>   	kfree(afu->err_irq_name);
> +	afu->serr_virq = 0;
>   }
> 
>   int cxl_native_register_psl_irq(struct cxl_afu *afu)
> @@ -1375,12 +1380,15 @@ int cxl_native_register_psl_irq(struct cxl_afu *afu)
> 
>   void cxl_native_release_psl_irq(struct cxl_afu *afu)
>   {
> -	if (afu->native->psl_virq != irq_find_mapping(NULL, afu->native->psl_hwirq))
> +	if (afu->native->psl_virq == 0 ||
> +	    afu->native->psl_virq !=
> +	    irq_find_mapping(NULL, afu->native->psl_hwirq))
>   		return;
> 
>   	cxl_unmap_irq(afu->native->psl_virq, afu);
>   	cxl_ops->release_one_irq(afu->adapter, afu->native->psl_hwirq);
>   	kfree(afu->psl_irq_name);
> +	afu->native->psl_virq = 0;
>   }
> 
>   static void recover_psl_err(struct cxl_afu *afu, u64 errstat)
> 

  parent reply	other threads:[~2017-06-06  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 16:56 [PATCH v2] cxl: Avoid double free_irq() for psl,slice interrupts Vaibhav Jain
2017-06-05  1:52 ` Andrew Donnellan
2017-06-06  8:09 ` Frederic Barrat [this message]
2017-06-06  9:17 ` Michael Ellerman
2017-06-08  4:05 ` [v2] " Michael Ellerman

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=4feb3b9f-d9a6-d6ae-ffff-d96c7a820b25@linux.vnet.ibm.com \
    --to=fbarrat@linux.vnet.ibm.com \
    --cc=alastair@au1.ibm.com \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=christophe_lombard@fr.ibm.com \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=imunsie@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=philippe.bergheaud@fr.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=vaibhav@linux.vnet.ibm.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 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).