All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: stable@vger.kernel.org
Subject: Re: Backport request
Date: Wed, 17 Jul 2019 08:01:47 +0900	[thread overview]
Message-ID: <20190716230147.GA23117@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1907162318380.1767@nanos.tec.linutronix.de>

On Wed, Jul 17, 2019 at 12:08:38AM +0200, Thomas Gleixner wrote:
> Folks!
> 
> There are more and more people worried about these usually harmless
> warnings:
> 
> 	do_IRQ: 0.39 No irq handler for vector
> 
> It took a while to figure out why that happens and why it is harmless for
> most interrupts, but there is also a real issue hidden for level type
> IOAPIC interrupts.
> 
> The following commits in Linus tree are addressing the issue:
> 
>  b7107a67f0d1 ("x86/irq: Handle spurious interrupt after shutdown gracefully")
>  dfe0cf8b51b0 ("x86/ioapic: Implement irq_get_irqchip_state() callback")
>  62e0468650c3 ("genirq: Add optional hardware synchronization for shutdown")
>  1d21f2af8571 ("genirq: Fix misleading synchronize_irq() documentation")
>  4001d8e8762f ("genirq: Delay deactivation in free_irq()")
> 
> There is another one which makes sense to be backported:
> 
>  f8a8fe61fec8 ("x86/irq: Seperate unused system vectors from spurious entry again")
> 
> These should go back to 4.19, but not farther.
> 
> They apply cleanly to 5.1 and 5.2. A backport to 4.19 is attached.

All now queued up, thanks for the backports!

greg k-h

  reply	other threads:[~2019-07-16 23:01 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 22:08 Backport request Thomas Gleixner
2019-07-16 23:01 ` Greg KH [this message]
2019-07-17 23:38 ` Sasha Levin
2019-07-18  7:57   ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2026-04-22 17:04 Josh Law
2026-04-23  4:55 ` Greg KH
2026-04-23  6:39   ` Krzysztof Kozlowski
2026-04-23  6:46     ` Greg KH
2026-04-23  7:02       ` Krzysztof Kozlowski
2026-04-23  7:56         ` Greg KH
2025-01-18  9:10 backport request Ard Biesheuvel
2025-01-18  9:27 ` Greg KH
2024-11-16 11:08 Backport request Hemdan, Hagar Gamal Halim
2024-11-16 13:51 ` Greg KH
2024-11-12 10:31 Hemdan, Hagar Gamal Halim
2024-11-15  5:10 ` Greg KH
2024-05-29  8:50 backport request Ard Biesheuvel
2024-06-06 13:10 ` Greg KH
2024-06-07  8:43   ` Ard Biesheuvel
2024-06-07 10:23     ` Greg KH
2024-06-07 10:25       ` Ard Biesheuvel
2024-06-07 10:27         ` Ard Biesheuvel
2024-06-07 10:46           ` Greg KH
2024-06-07 10:49             ` Ard Biesheuvel
2024-05-16 10:16 Backport request Hemdan, Hagar Gamal Halim
2024-05-22 15:45 ` Greg KH
2023-08-01  7:17 Hemdan, Hagar Gamal Halim
2023-08-01  7:24 ` Greg KH
2023-07-25 11:13 backport request Ard Biesheuvel
2023-07-25 11:17 ` Ard Biesheuvel
2023-07-25 12:29 ` Greg KH
2023-07-25 12:51   ` Ard Biesheuvel
2023-07-25 13:21     ` Greg KH
2023-07-25 13:25       ` Ard Biesheuvel
2023-07-25 13:41         ` Greg KH
2023-07-25 13:48           ` Ard Biesheuvel
2023-07-27 10:59 ` Greg KH
2022-08-24 11:20 Backport request Juergen Gross
2022-08-24 12:10 ` Greg Kroah-Hartman
2022-08-24 13:52   ` Juergen Gross
2022-08-25 11:59     ` Greg Kroah-Hartman
2020-12-15 16:02 Daniel Vetter
2020-12-19 12:42 ` Greg KH
2020-12-19 13:56   ` Daniel Vetter
2018-02-28 13:56 Corey Minyard
2018-02-28 14:18 ` Greg KH
2017-03-01 12:31 Juergen Gross
2017-03-21  7:58 ` Juergen Gross
2017-04-05 13:24 ` Ian Jackson
2014-01-13  9:49 Andrew Cooper
2014-01-13 10:47 ` David Vrabel
2014-01-13 11:13 ` Jan Beulich
2014-01-13 11:30   ` David Vrabel
2014-01-13 11:36     ` Jan Beulich
2014-01-13 13:38       ` Daniel Kiper

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=20190716230147.GA23117@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --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.