From: alex@ash.works
To: David Arcari <darcari@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Jerry Hoemann <jerry.hoemann@hpe.com>,
alexander.shishkin@linux.intel.com, alex@ash.works
Subject: Re: [PATCH] intel_th: core: fix null pointer dereference in intel_th_irq
Date: Fri, 26 Sep 2025 19:19:11 +0300 [thread overview]
Message-ID: <61a6cca8379529c49a031d51f90d2da6@linux.intel.com> (raw)
In-Reply-To: <20250825174554.925679-1-darcari@redhat.com>
On 2025-08-25 20:45, David Arcari wrote:
> In certain cases intel_th_irq can reference a null entry in
> the th->thdev array. This results in the splat shown below.
> The problem is that intel_th_output_enable() can modify the
> thdev[] array at the same time intel_th_irq is referencing
> the same array. This can be fixed by disabling interrupts
> during the call to intel_th_output_enable().
Hi David,
Thank you for the bug report and rootcausing! Can you please also
detail the sequence of actions by which this is reproduced, so
that I can test my fix and not bother you with a back-and-forth
over-email debugging and also add it to our regression testing?
Doesn't have to be a shell script (although I wouldn't say no
to that), plain english would work in a pinch. If you have the
time, I'm also curious about your use case for intel_th.
This has eluded our testing for about 10 years, so I'm very
interested in the reproducer.
> BUG: kernel NULL pointer dereference, address: 0000000000000304
> Oops: Oops: 0000 [#1] SMP NOPTI
> RIP: 0010:intel_th_irq+0x26/0x70 [intel_th]
Yes, this is absolutely a bug.
> @@ -715,7 +715,9 @@ intel_th_subdevice_alloc(struct intel_th *th,
> int intel_th_output_enable(struct intel_th *th, unsigned int otype)
> {
> struct intel_th_device *thdev;
> - int src = 0, dst = 0;
> + int src = 0, dst = 0, ret = 0;
> +
> + disable_irq(th->irq);
>
> for (src = 0, dst = 0; dst <= th->num_thdevs; src++, dst++) {
> for (; src < ARRAY_SIZE(intel_th_subdevices); src++) {
[...]
> @@ -750,16 +752,19 @@ int intel_th_output_enable(struct intel_th *th,
> unsigned int otype)
> goto found;
> }
>
> +nodev:
> + enable_irq(th->irq);
> return -ENODEV;
>
> found:
> thdev = intel_th_subdevice_alloc(th, &intel_th_subdevices[src]);
> if (IS_ERR(thdev))
> - return PTR_ERR(thdev);
> -
> - th->thdev[th->num_thdevs++] = thdev;
> + ret = PTR_ERR(thdev);
> + else
> + th->thdev[th->num_thdevs++] = thdev;
>
> - return 0;
> + enable_irq(th->irq);
> + return ret;
> }
> EXPORT_SYMBOL_GPL(intel_th_output_enable);
This is indeed a possible fix, but I believe a little bit of
serialization can be employed here.
Lastly, my apologies for tardiness.
Thanks!
--
Alex
next prev parent reply other threads:[~2025-09-26 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 17:45 [PATCH] intel_th: core: fix null pointer dereference in intel_th_irq David Arcari
2025-09-04 17:41 ` David Arcari
2025-09-26 16:19 ` alex [this message]
2025-09-26 20:12 ` David Arcari
2025-09-27 14:54 ` Markus Elfring
2025-09-29 12:05 ` David Arcari
2025-11-18 21:21 ` [PATCH v2] " David Arcari
2025-11-19 12:55 ` Markus Elfring
2025-11-20 12:32 ` David Arcari
2025-11-20 13:07 ` [v2] " Markus Elfring
2025-11-20 13:22 ` David Arcari
2026-01-16 12:49 ` Alexander Shishkin
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=61a6cca8379529c49a031d51f90d2da6@linux.intel.com \
--to=alex@ash.works \
--cc=alexander.shishkin@linux.intel.com \
--cc=darcari@redhat.com \
--cc=jerry.hoemann@hpe.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox