From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Jon Derrick <jonathan.derrick@intel.com>
Subject: Re: [PATCH v2] vmd: Fix infinite loop executing irq's
Date: Tue, 23 Aug 2016 16:36:05 -0500 [thread overview]
Message-ID: <20160823213605.GC5838@localhost> (raw)
In-Reply-To: <1470671271-22465-1-git-send-email-keith.busch@intel.com>
Hi Keith,
On Mon, Aug 08, 2016 at 09:47:51AM -0600, Keith Busch wrote:
> We can't initialize the list head on deletion as this causes the node
> to point to itself, looping infinitely if the vmd IRQ handler happened
> to be servicing that node.
>
> The list initialization was trying fix a bug from multiple calls to
> disable the same IRQ. We can fix this instead by having the vmd driver
> track if the interrupt is enabled.
>
> Signed-off-by: Keith Busch <keith.busch@intel.com>
> Cc: Jon Derrick <jonathan.derrick@intel.com>
> Reported-by: Grzegorz Koczot <grzegorz.koczot@intel.com>
> Tested-by: Miroslaw Drost <miroslaw.drost@intel.com>
I assume you want
Fixes: 97e923063575 ("x86/PCI: VMD: Initialize list item in IRQ disable")
and you want this in for-linus so it goes in v4.8 instead of v4.9.
I did that for you, so let me know if it's not right.
> ---
> v1 -> v2:
>
> Removed check for poisioned list pointer. This is abusing knowledge
> internal to the list api, so we need another way to know if the child
> irq is enabled. This patch uses a driver controlled boolean for this.
>
> Added tags for the bug reporter and tester.
>
> arch/x86/pci/vmd.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/pci/vmd.c b/arch/x86/pci/vmd.c
> index e88b417..4b85837 100644
> --- a/arch/x86/pci/vmd.c
> +++ b/arch/x86/pci/vmd.c
> @@ -41,6 +41,7 @@ static DEFINE_RAW_SPINLOCK(list_lock);
> * @node: list item for parent traversal.
> * @rcu: RCU callback item for freeing.
> * @irq: back pointer to parent.
> + * @enabled: true if driver enabled irq
> * @virq: the virtual IRQ value provided to the requesting driver.
> *
> * Every MSI/MSI-X IRQ requested for a device in a VMD domain will be mapped to
> @@ -50,6 +51,7 @@ struct vmd_irq {
> struct list_head node;
> struct rcu_head rcu;
> struct vmd_irq_list *irq;
> + bool enabled;
> unsigned int virq;
> };
>
> @@ -122,7 +124,9 @@ static void vmd_irq_enable(struct irq_data *data)
> unsigned long flags;
>
> raw_spin_lock_irqsave(&list_lock, flags);
> + WARN_ON(vmdirq->enabled);
> list_add_tail_rcu(&vmdirq->node, &vmdirq->irq->irq_list);
> + vmdirq->enabled = true;
> raw_spin_unlock_irqrestore(&list_lock, flags);
>
> data->chip->irq_unmask(data);
> @@ -136,8 +140,10 @@ static void vmd_irq_disable(struct irq_data *data)
> data->chip->irq_mask(data);
>
> raw_spin_lock_irqsave(&list_lock, flags);
> - list_del_rcu(&vmdirq->node);
> - INIT_LIST_HEAD_RCU(&vmdirq->node);
> + if (vmdirq->enabled) {
> + list_del_rcu(&vmdirq->node);
> + vmdirq->enabled = false;
> + }
> raw_spin_unlock_irqrestore(&list_lock, flags);
> }
>
> --
> 2.7.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-08-23 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 15:47 [PATCH v2] vmd: Fix infinite loop executing irq's Keith Busch
2016-08-08 17:05 ` Jon Derrick
2016-08-23 21:36 ` Bjorn Helgaas [this message]
2016-08-23 22:10 ` Keith Busch
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=20160823213605.GC5838@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).