From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>, Marc Zyngier <maz@kernel.org>
Subject: [GIT PULL] IRQ fix
Date: Sat, 25 May 2024 12:48:05 +0200 [thread overview]
Message-ID: <ZlHB5UO55nTuG6II@gmail.com> (raw)
Linus,
Please pull the latest irq/urgent Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-2024-05-25
# HEAD: b84a8aba806261d2f759ccedf4a2a6a80a5e55ba genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after()
Misc fixes:
- Fix x86 IRQ vector leak caused by a CPU offlining race
- Fix build failure in the riscv-imsic irqchip driver
caused by an API-change semantic conflict
- Fix use-after-free in irq_find_at_or_after()
Thanks,
Ingo
------------------>
Dongli Zhang (1):
genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline
Palmer Dabbelt (1):
irqchip/riscv-imsic: Fixup riscv_ipi_set_virq_range() conflict
dicken.ding (1):
genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after()
arch/x86/kernel/apic/vector.c | 9 ++++++---
drivers/irqchip/irq-riscv-imsic-early.c | 2 +-
kernel/irq/cpuhotplug.c | 16 ++++++++--------
kernel/irq/irqdesc.c | 5 ++++-
4 files changed, 19 insertions(+), 13 deletions(-)
next reply other threads:[~2024-05-25 10:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 10:48 Ingo Molnar [this message]
2024-05-25 21:53 ` [GIT PULL] IRQ fix pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-11-15 9:09 Ingo Molnar
2025-11-15 18:26 ` pr-tracker-bot
2025-04-26 8:28 Ingo Molnar
2025-04-26 17:05 ` pr-tracker-bot
2025-02-08 9:12 Ingo Molnar
2025-02-08 20:07 ` pr-tracker-bot
2024-12-29 8:40 Ingo Molnar
2024-12-29 18:22 ` pr-tracker-bot
2024-05-05 9:06 Ingo Molnar
2024-05-05 19:43 ` pr-tracker-bot
2024-04-28 8:05 Ingo Molnar
2024-04-28 19:28 ` pr-tracker-bot
2024-04-14 7:54 Ingo Molnar
2024-04-14 18:48 ` pr-tracker-bot
2024-03-18 9:40 Ingo Molnar
2024-03-18 16:48 ` pr-tracker-bot
2023-10-28 13:17 Ingo Molnar
2023-10-28 18:17 ` pr-tracker-bot
2021-05-15 7:44 Ingo Molnar
2021-05-15 17:55 ` pr-tracker-bot
2020-01-18 17:19 Ingo Molnar
2020-01-18 21:05 ` pr-tracker-bot
2019-09-12 8:35 Ingo Molnar
2019-09-12 10:15 ` pr-tracker-bot
2017-11-05 14:37 Ingo Molnar
2017-03-07 20:24 Ingo Molnar
2016-12-23 22:46 Ingo Molnar
2016-11-14 7:59 Ingo Molnar
2016-10-28 8:33 [GIT PULL] irq fix Ingo Molnar
2016-08-12 19:22 [GIT PULL] IRQ fix Ingo Molnar
2016-01-08 12:42 [GIT PULL] irq fix Ingo Molnar
2015-05-15 7:13 Ingo Molnar
2014-04-16 12:59 Ingo Molnar
2013-10-04 7:51 Ingo Molnar
2012-08-03 16:37 Ingo Molnar
2011-12-05 19:03 Ingo Molnar
2011-06-13 9:51 Ingo Molnar
2011-05-03 11:48 Ingo Molnar
2011-04-22 13:33 Ingo Molnar
2011-04-07 17:46 Ingo Molnar
2011-02-03 17:14 Ingo Molnar
2010-12-08 8:05 Ingo Molnar
2009-11-10 17:50 Ingo Molnar
2009-08-10 18:15 Ingo Molnar
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=ZlHB5UO55nTuG6II@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).