stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Nadav Haklai <nadavh@marvell.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Antoine Tenart <antoine.tenart@bootlin.com>,
	Stefan Chulski <stefanc@marvell.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH] platform-msi: Free descriptors in platform_msi_domain_free()
Date: Thu, 20 Sep 2018 19:39:21 +0100	[thread overview]
Message-ID: <86r2hovwrq.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <20180907150129.14729-1-miquel.raynal@bootlin.com>

Hi Miquel,

On Fri, 07 Sep 2018 16:01:29 +0100,
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> 
> Since the addition of platform MSI support, there were two helpers
> supposed to allocate/free IRQs for a device:
> 
>     platform_msi_domain_alloc_irqs()
>     platform_msi_domain_free_irqs()
> 
> In these helpers, IRQ descriptors are allocated in the "alloc" routine
> while they are freed in the "free" one.
> 
> Later, two other helpers have been added to handle IRQ domains on top
> of MSI domains:
> 
>     platform_msi_domain_alloc()
>     platform_msi_domain_free()
> 
> Seen from the outside, the logic is pretty close with the former
> helpers and people used it with the same logic as before: a
> platform_msi_domain_alloc() call should be balanced with a
> platform_msi_domain_free() call. While this is probably what was
> intended to do, the platform_msi_domain_free() does not remove/free
> the IRQ descriptor(s) created/inserted in
> platform_msi_domain_alloc().
> 
> One effect of such situation is that removing a module that requested
> an IRQ will let one orphaned IRQ descriptor (with an allocated MSI
> entry) in the device descriptors list. Next time the module will be
> inserted back, one will observe that the allocation will happen twice
> in the MSI domain, one time for the remaining descriptor, one time for
> the new one. It also has the side effect to quickly overshoot the
> maximum number of allocated MSI and then prevent any module requesting
> an interrupt in the same domain to be inserted anymore.
> 
> This situation has been met with loops of insertion/removal of the
> mvpp2.ko module (requesting 15 MSIs each time).
> 
> Fixes: 552c494a7666 ("platform-msi: Allow creation of a MSI-based stacked irq domain")
> Cc: stable@vger.kernel.org
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
>  drivers/base/platform-msi.c | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/drivers/base/platform-msi.c b/drivers/base/platform-msi.c
> index 60d6cc618f1c..b9d9d1729215 100644
> --- a/drivers/base/platform-msi.c
> +++ b/drivers/base/platform-msi.c
> @@ -354,6 +354,20 @@ platform_msi_create_device_domain(struct device *dev,
>  	return NULL;
>  }
>  
> +static void platform_msi_domain_free_descs(struct irq_domain *domain, int virq,
> +					   int nvec)
> +{
> +	struct platform_msi_priv_data *data = domain->host_data;
> +	struct msi_desc *desc, *tmp;
> +
> +	list_for_each_entry_safe(desc, tmp, dev_to_msi_list(data->dev), list) {
> +		if (desc->irq >= virq && desc->irq < (virq + nvec)) {
> +			list_del(&desc->list);
> +			free_msi_entry(desc);
> +		}
> +	}
> +}
> +
>  /**
>   * platform_msi_domain_free - Free interrupts associated with a platform-msi
>   *                            domain
> @@ -375,6 +389,8 @@ void platform_msi_domain_free(struct irq_domain *domain, unsigned int virq,
>  
>  		irq_domain_free_irqs_common(domain, desc->irq, 1);
>  	}
> +
> +	platform_msi_domain_free_descs(domain, virq, nvec);
>  }
>  
>  /**
> -- 
> 2.17.1
> 

Good catch, but I wonder why you don't use the existing
helper instead. Something like this (untested):

diff --git a/drivers/base/platform-msi.c b/drivers/base/platform-msi.c
index 60d6cc618f1c..87808ac08bfb 100644
--- a/drivers/base/platform-msi.c
+++ b/drivers/base/platform-msi.c
@@ -375,6 +375,8 @@ void platform_msi_domain_free(struct irq_domain *domain, unsigned int virq,
 
 		irq_domain_free_irqs_common(domain, desc->irq, 1);
 	}
+
+	platform_msi_free_descs(data->dev, virq, nvec);
 }
 
 /**

Thanks,

	M.

-- 
Jazz is not dead, it just smell funny.

  reply	other threads:[~2018-09-21  0:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 15:01 [PATCH] platform-msi: Free descriptors in platform_msi_domain_free() Miquel Raynal
2018-09-20 18:39 ` Marc Zyngier [this message]
2018-09-24 13:39   ` Miquel Raynal
2018-09-28  8:34     ` Marc Zyngier
2018-09-28 15:10       ` Miquel Raynal
     [not found]         ` <86k1moubgr.wl-marc.zyngier@arm.com>
2018-10-11  9:17           ` Miquel Raynal

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=86r2hovwrq.wl-marc.zyngier@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=antoine.tenart@bootlin.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gregory.clement@bootlin.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=nadavh@marvell.com \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stefanc@marvell.com \
    --cc=thomas.petazzoni@bootlin.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).