mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Felipe Calliari <calliarifelipe@gmail.com>
Cc: linux-media@vger.kernel.org,
	Antti Laakso <antti.laakso@linux.intel.com>,
	"Sapre, Sarang" <sarang.sapre@intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Tomas Moro <tmorolias@gmail.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 2/2] media: ipu6: Only call the isys and psys ISRs for their own interrupts
Date: Thu, 24 Sep 2026 13:46:44 +0300	[thread overview]
Message-ID: <arT_lPROASv1Ps8l@kekkonen.localdomain> (raw)
In-Reply-To: <20260923234224.325504-3-calliarifelipe@gmail.com>

Hi Felipe,

Thanks for the patch.

On Wed, Sep 23, 2026 at 08:42:24PM -0300, Felipe Calliari wrote:
> ipu6_buttress_isr() calls the isys and psys ISRs on every buttress
> interrupt, and only afterwards checks whether the interrupt was theirs.
> So each isys interrupt also runs the psys ISR, and each psys interrupt
> runs the isys ISR, only to have the result discarded.
> 
> Beyond the wasted work, this makes an interrupt for one device
> dereference the other device's hooks. After intel_ipu6_psys is unloaded,
> its adev->auxdrv_data still points into the unloaded module, and every
> isys interrupt, e.g. on the next stream, calls through it. This matches
> a hard lockup without a trace reported on the first stream after
> unloading the psys driver. On a Samsung Galaxy Book3 Ultra,
> instrumenting the ISR showed that a 60-frame capture after
> "rmmod intel_ipu6_psys" would have made at least ten calls through the
> stale psys hooks. The same capture made none with this change, and
> captured all 60 frames.

The problem here is a dangling pointer. Can you also post a patch to set
that drvdata to NULL?

The above paragraph isn't relevant in the context of this patch.

> 
> Check the interrupt status bit before calling the ISR.
> 
> Reported-by: Mars-Wave <tmorolias@gmail.com>
> Closes: https://lore.kernel.org/linux-media/20260922063507.690-1-tmorolias@gmail.com/
> Fixes: ab29a2478e70 ("media: intel/ipu6: add IPU6 buttress interface driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Felipe Calliari <calliarifelipe@gmail.com>
> ---
>  drivers/media/pci/intel/ipu6/ipu6-buttress.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/media/pci/intel/ipu6/ipu6-buttress.c b/drivers/media/pci/intel/ipu6/ipu6-buttress.c
> index 63197f746..74c191d72 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6-buttress.c
> +++ b/drivers/media/pci/intel/ipu6/ipu6-buttress.c
> @@ -369,11 +369,13 @@ irqreturn_t ipu6_buttress_isr(int irq, void *isp_ptr)
>  		writel(irq_status, isp->base + regs->irq_clear);
>  
>  		for (i = 0; i < ARRAY_SIZE(adev_irq_mask); i++) {
> -			irqreturn_t r = ipu6_buttress_call_isr(adev[i]);
> +			irqreturn_t r;
>  
>  			if (!(irq_status & adev_irq_mask[i]))
>  				continue;
>  
> +			r = ipu6_buttress_call_isr(adev[i]);
> +

No need for this newline.

>  			if (r == IRQ_WAKE_THREAD) {
>  				ret = IRQ_WAKE_THREAD;
>  				disable_irqs |= adev_irq_mask[i];

-- 
Regards,

Sakari Ailus

      reply	other threads:[~2026-09-24 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 23:42 [PATCH 0/2] media: ipu6: Stop calling ISR hooks of unloaded drivers Felipe Calliari
2026-09-23 23:42 ` [PATCH 1/2] media: ipu6: Clear the isys ISR hooks when the isys driver goes away Felipe Calliari
2026-09-24 11:46   ` Sakari Ailus
2026-09-23 23:42 ` [PATCH 2/2] media: ipu6: Only call the isys and psys ISRs for their own interrupts Felipe Calliari
2026-09-24 10:46   ` Sakari Ailus [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=arT_lPROASv1Ps8l@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=antti.laakso@linux.intel.com \
    --cc=calliarifelipe@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sarang.sapre@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=tmorolias@gmail.com \
    /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

all inboxes | Powered by JetHome®