From: Thomas Gleixner <tglx@linutronix.de>
To: Ben Luo <luoben@linux.alibaba.com>
Cc: alex.williamson@redhat.com, linux-kernel@vger.kernel.org,
tao.ma@linux.alibaba.com, gerry@linux.alibaba.com,
nanhai.zou@linux.alibaba.com, linyunsheng@huawei.com
Subject: Re: [PATCH v3 1/3] genirq: enhance error recovery code in free irq
Date: Thu, 15 Aug 2019 16:20:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908151617150.1908@nanos.tec.linutronix.de> (raw)
In-Reply-To: <ac85d5f69649cb2b2c9e9254207fd751274bf3ad.1565857737.git.luoben@linux.alibaba.com>
On Thu, 15 Aug 2019, Ben Luo wrote:
> Per Thomas Gleixner's comments:
> 1) free_irq/free_percpu_irq returns if called from IRQ context
> 2) move WARN out of the locked region and print out dev_id
Please do not describe WHAT the patch is doing, please describe WHY.
> Signed-off-by: Ben Luo <luoben@linux.alibaba.com>
> ---
> kernel/irq/manage.c | 32 ++++++++++++++++++++------------
> 1 file changed, 20 insertions(+), 12 deletions(-)
>
> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> index e8f7f17..6f9b20f 100644
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -1690,7 +1690,11 @@ static struct irqaction *__free_irq(struct irq_desc *desc, void *dev_id)
> struct irqaction *action, **action_ptr;
> unsigned long flags;
>
> - WARN(in_interrupt(), "Trying to free IRQ %d from IRQ context!\n", irq);
> + if (in_interrupt()) {
> + WARN(1, "Trying to free IRQ %d (dev_id %p) from IRQ context!\n",
> + irq, dev_id);
> + return NULL;
> + }
if (WARN(in_interrupt(), ."Tr...."))
return NULL;
Thanks,
tglx
next prev parent reply other threads:[~2019-08-15 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 13:02 [PATCH v3 0/3] genirq/vfio: Introduce update_irq_devid and optimize VFIO irq ops Ben Luo
2019-08-15 13:02 ` [PATCH v3 1/3] genirq: enhance error recovery code in free irq Ben Luo
2019-08-15 14:20 ` Thomas Gleixner [this message]
2019-08-15 13:03 ` [PATCH v3 2/3] genirq: introduce update_irq_devid() Ben Luo
2019-08-15 14:58 ` Thomas Gleixner
2019-08-19 5:31 ` luoben
2019-08-19 8:18 ` Thomas Gleixner
2019-08-15 13:03 ` [PATCH v3 3/3] vfio_pci: make use of update_irq_devid and optimize irq ops Ben Luo
2019-08-15 16:45 ` Thomas Gleixner
[not found] ` <7a3606ad-8fa6-45d5-b5a4-ee3f07893a25@linux.alibaba.com>
2019-08-20 15:27 ` Liu, Jiang
2019-08-22 13:41 ` luoben
2019-08-19 20:51 ` [PATCH v3 0/3] genirq/vfio: Introduce update_irq_devid and optimize VFIO " Alex Williamson
2019-08-20 4:03 ` luoben
2019-08-20 15:22 ` Alex Williamson
2019-08-20 15:51 ` luoben
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=alpine.DEB.2.21.1908151617150.1908@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=alex.williamson@redhat.com \
--cc=gerry@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=luoben@linux.alibaba.com \
--cc=nanhai.zou@linux.alibaba.com \
--cc=tao.ma@linux.alibaba.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
all inboxes | Powered by JetHome®