[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220325013359.2691092-1-chenlifu@huawei.com>
Date: Fri, 25 Mar 2022 09:33:59 +0800
From: Chen Lifu <chenlifu@...wei.com>
To: <tglx@...utronix.de>, <linux-kernel@...r.kernel.org>
Subject: [PATCH -next] irq: print depth in __enable_irq WARNING
Since case 0 and 1 of desc->depth may print same warning messages as follows,
according to the messages, we do not know in which case the warning is generated.
This patch prints extra desc->depth in the warning messages to distinguish
these cases.
This patch just does warning message changes,no functional changes.
[20220314100142]------------[ cut here ]------------
[20220314100142]WARNING: CPU: 1 PID: 10332 at kernel/irq/manage.c:723 __enable_irq+0x58/0xa4
[20220314100142]Unbalanced enable for IRQ 38
......
Signed-off-by: Chen Lifu <chenlifu@...wei.com>
---
kernel/irq/manage.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index c03f71d5ec10..83bb9d9ee71a 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -769,12 +769,12 @@ void disable_nmi_nosync(unsigned int irq)
void __enable_irq(struct irq_desc *desc)
{
switch (desc->depth) {
case 0:
err_out:
- WARN(1, KERN_WARNING "Unbalanced enable for IRQ %d\n",
- irq_desc_get_irq(desc));
+ WARN(1, KERN_WARNING "depth %u: Unbalanced enable for IRQ %d\n",
+ desc->depth, irq_desc_get_irq(desc));
break;
case 1: {
if (desc->istate & IRQS_SUSPENDED)
goto err_out;
/* Prevent probing on this irq: */
--
2.35.1
Powered by blists - more mailing lists