From: Greg KH <gregkh@linuxfoundation.org>
To: Rishabh Bhatnagar <risbhat@amazon.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, tglx@linutronix.de,
mingo@redhat.com, linux-kernel@vger.kernel.org, benh@amazon.com,
mbacco@amazon.com
Subject: Re: [PATCH 0/6] IRQ handling patches backport to 4.14 stable
Date: Thu, 27 Oct 2022 12:13:01 +0200 [thread overview]
Message-ID: <Y1pZrdySrzod3NCM@kroah.com> (raw)
In-Reply-To: <20220929210651.12308-1-risbhat@amazon.com>
On Thu, Sep 29, 2022 at 09:06:45PM +0000, Rishabh Bhatnagar wrote:
> This patch series backports a bunch of patches related IRQ handling
> with respect to freeing the irq line while IRQ is in flight at CPU
> or at the hardware level.
> Recently we saw this issue in serial 8250 driver where the IRQ was being
> freed while the irq was in flight or not yet delivered to the CPU. As a
> result the irqchip was going into a wedged state and IRQ was not getting
> delivered to the cpu. These patches helped fixed the issue in 4.14
> kernel.
> Let us know if more patches need backporting.
>
> Lukas Wunner (2):
> genirq: Update code comments wrt recycled thread_mask
> genirq: Synchronize only with single thread on free_irq()
>
> Thomas Gleixner (4):
> genirq: Delay deactivation in free_irq()
> genirq: Fix misleading synchronize_irq() documentation
> genirq: Add optional hardware synchronization for shutdown
> x86/ioapic: Implement irq_get_irqchip_state() callback
>
> arch/x86/kernel/apic/io_apic.c | 46 ++++++++++++++
> kernel/irq/autoprobe.c | 6 +-
> kernel/irq/chip.c | 6 ++
> kernel/irq/cpuhotplug.c | 2 +-
> kernel/irq/internals.h | 5 ++
> kernel/irq/manage.c | 106 ++++++++++++++++++++++-----------
> 6 files changed, 133 insertions(+), 38 deletions(-)
A simple build test breaks with this series applied:
ld: kernel/irq/manage.o: in function `__synchronize_hardirq':
manage.c:(.text+0x149): undefined reference to `__irq_get_irqchip_state'
ld: kernel/irq/manage.o: in function `irq_get_irqchip_state':
manage.c:(.text+0x5a2): undefined reference to `__irq_get_irqchip_state'
make: *** [Makefile:1038: vmlinux] Error 1
How did you test this?
{sigh}
I'm dropping all of these from my queue. I think you need to just keep
this in your device-specific tree as obviously this is not ready to be
backported anywhere.
greg k-h
prev parent reply other threads:[~2022-10-27 10:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 21:06 [PATCH 0/6] IRQ handling patches backport to 4.14 stable Rishabh Bhatnagar
2022-09-29 21:06 ` [PATCH 1/6] genirq: Update code comments wrt recycled thread_mask Rishabh Bhatnagar
2022-09-29 21:06 ` [PATCH 2/6] genirq: Synchronize only with single thread on free_irq() Rishabh Bhatnagar
2022-09-29 21:06 ` [PATCH 3/6] genirq: Delay deactivation in free_irq() Rishabh Bhatnagar
2022-09-29 21:06 ` [PATCH 4/6] genirq: Fix misleading synchronize_irq() documentation Rishabh Bhatnagar
2022-09-29 21:06 ` [PATCH 5/6] genirq: Add optional hardware synchronization for shutdown Rishabh Bhatnagar
2022-09-29 21:06 ` [PATCH 6/6] x86/ioapic: Implement irq_get_irqchip_state() callback Rishabh Bhatnagar
2022-10-02 15:30 ` [PATCH 0/6] IRQ handling patches backport to 4.14 stable Greg KH
2022-10-03 17:54 ` Bhatnagar, Rishabh
2022-10-07 3:07 ` Herrenschmidt, Benjamin
2022-10-09 17:50 ` Bhatnagar, Rishabh
2022-10-14 19:00 ` Bhatnagar, Rishabh
2022-10-15 15:36 ` gregkh
2022-10-27 10:13 ` Greg KH [this message]
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=Y1pZrdySrzod3NCM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benh@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbacco@amazon.com \
--cc=mingo@redhat.com \
--cc=risbhat@amazon.com \
--cc=sashal@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox