All of lore.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Thomas Gleixner <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, mingo@kernel.org, hpa@zytor.com,
	linux-kernel@vger.kernel.org, mroos@linux.ee
Subject: [tip:irq/urgent] genirq: Make legacy autoprobing work again
Date: Thu, 1 Feb 2018 01:58:13 -0800	[thread overview]
Message-ID: <tip-9bc43be5151aaf1aa87f832128f1687341f07483@git.kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1801301935410.1797@nanos>

Commit-ID:  9bc43be5151aaf1aa87f832128f1687341f07483
Gitweb:     https://git.kernel.org/tip/9bc43be5151aaf1aa87f832128f1687341f07483
Author:     Thomas Gleixner <tglx@linutronix.de>
AuthorDate: Tue, 30 Jan 2018 19:36:32 +0100
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 1 Feb 2018 10:54:48 +0100

genirq: Make legacy autoprobing work again

Meelis reported the following warning on a quad P3 HP NetServer museum piece:

WARNING: CPU: 3 PID: 258 at kernel/irq/chip.c:244 __irq_startup+0x80/0x100
EIP: __irq_startup+0x80/0x100
irq_startup+0x7e/0x170
probe_irq_on+0x128/0x2b0
parport_irq_probe.constprop.18+0x8d/0x1af [parport_pc]
parport_pc_probe_port+0xf11/0x1260 [parport_pc]
parport_pc_init+0x78a/0xf10 [parport_pc]
parport_parse_param.constprop.16+0xf0/0xf0 [parport_pc]
do_one_initcall+0x45/0x1e0

This is caused by the rewrite of the irq activation/startup sequence which
missed to convert a callsite in the irq legacy auto probing code.

To fix this irq_activate_and_startup() needs to gain a return value so the
pending logic can work proper.

Fixes: c942cee46bba ("genirq: Separate activation and startup")
Reported-by: Meelis Roos <mroos@linux.ee>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Meelis Roos <mroos@linux.ee>
Cc: stable@vger.kernel.org
Link: https://lkml.kernel.org/r/alpine.DEB.2.20.1801301935410.1797@nanos
---
 kernel/irq/chip.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index f681c0e..c69357a 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -297,7 +297,7 @@ int irq_activate(struct irq_desc *desc)
 int irq_activate_and_startup(struct irq_desc *desc, bool resend)
 {
 	if (WARN_ON(irq_activate(desc)))
-		return;
+		return 0;
 	return irq_startup(desc, resend, IRQ_START_FORCE);
 }
 

  parent reply	other threads:[~2018-02-01 10:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 16:20 4.15: WARNING: CPU: 3 PID: 258 at kernel/irq/chip.c:244 __irq_startup+0x80/0x100 Meelis Roos
2018-01-29 16:35 ` Thomas Gleixner
2018-01-30 18:36   ` Thomas Gleixner
2018-01-31  7:21     ` Meelis Roos
2018-01-31  7:58       ` Thomas Gleixner
2018-01-31  8:09         ` Ingo Molnar
2018-01-31 11:23           ` Meelis Roos
2018-01-31 11:59             ` Ingo Molnar
2018-01-31  9:54     ` [tip:irq/urgent] genirq: Make legacy autoprobing work again tip-bot for Thomas Gleixner
2018-02-01  8:15       ` Geert Uytterhoeven
2018-02-01  9:56         ` Thomas Gleixner
2018-02-01 11:35         ` Arnd Bergmann
2018-02-01  9:58     ` tip-bot for Thomas Gleixner [this message]
2018-02-01 10:12     ` tip-bot for Thomas Gleixner

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=tip-9bc43be5151aaf1aa87f832128f1687341f07483@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mroos@linux.ee \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.