From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
falemi@asu.edu, linux-kernel@vger.kernel.org
Subject: Re: [BUG] free_irq -- mei_me_probe error path frees an IRQ it never acquired
Date: Fri, 28 Aug 2026 07:33:21 +0200 [thread overview]
Message-ID: <2026082854-blasphemy-freeload-5fb8@gregkh> (raw)
In-Reply-To: <CA+0ovCiBsLEjFZ7-=MGtMQix8HMgsp5WQJbVqb70dPqyHSZiTQ@mail.gmail.com>
On Thu, Aug 27, 2026 at 08:20:16PM -0700, Farhad Alemi wrote:
> Hello,
>
> As part of the kernel research at ASU's SEFCOM
> lab, we hit the crash below. Crash reports can be found here:
>
> https://github.com/farhad-alemi/public_bug_reports/tree/main/130-mei_me-free_irq-never-acquired/
>
> genirq: Flags mismatch irq 0. 00000080 (mei_me) vs. 00215a00 (timer)
> mei_me 0000:00:01.0: request_threaded_irq failure. irq = 0
> Trying to free already-free IRQ 0
> WARNING: kernel/irq/manage.c:1879 at __free_irq
> kernel/irq/manage.c:1879 [inline], CPU#1: kworker/u10:0/27
> WARNING: kernel/irq/manage.c:1879 at free_irq+0x292/0x8b0
> kernel/irq/manage.c:2018, CPU#1: kworker/u10:0/27
> Workqueue: async async_run_entry_fn
> Call Trace:
> free_irq+0x292/0x8b0 kernel/irq/manage.c:2018
> mei_me_probe+0x672/0x820 drivers/misc/mei/pci-me.c:295
> pci_device_probe+0x461/0xa50 drivers/pci/pci-driver.c:489
> really_probe+0x267/0xaf0 drivers/base/dd.c:709
> driver_probe_device+0x4f/0x240 drivers/base/dd.c:901
> __driver_attach_async_helper+0x128/0x290 drivers/base/dd.c:1227
>
> Our reproducer.c is available upon request.
>
> Happy to test a patch if that would help.
Please send a patch to fix this, as you have a reproducer, and your tool
can generate it quite easily.
thanks,
greg k-h
prev parent reply other threads:[~2026-08-28 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 3:20 [BUG] free_irq -- mei_me_probe error path frees an IRQ it never acquired Farhad Alemi
2026-08-28 5:33 ` Greg Kroah-Hartman [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=2026082854-blasphemy-freeload-5fb8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=linux-kernel@vger.kernel.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 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.