Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: intel-xe@lists.freedesktop.org, badal.nilawar@intel.com
Subject: Re: [PATCH v1] drm/xe/i2c: Disable IRQ on unbind
Date: Fri, 11 Sep 2026 13:17:14 +0200	[thread overview]
Message-ID: <aqPjOgEgFG04B_ef@black.igk.intel.com> (raw)
In-Reply-To: <20260911044021.2393342-1-raag.jadav@intel.com>

On Fri, Sep 11, 2026 at 10:10:21AM +0530, Raag Jadav wrote:
> Currently, struct xe_i2c is freed before SGUnit IRQ is disabled, leaving
> a potential UAF in case the IRQ is hit in that small window. Explicitly
> disable I2C IRQ as part of xe_i2c_remove() and fix this.
> 
> Fixes: 0bb78ce09926 ("drm/xe/i2c: Wire up reset/postinstall for I2C IRQ")
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>

FWIW:

Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>

> ---
>  drivers/gpu/drm/xe/xe_i2c.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_i2c.c b/drivers/gpu/drm/xe/xe_i2c.c
> index d8fa68206f41..82b22c5412ba 100644
> --- a/drivers/gpu/drm/xe/xe_i2c.c
> +++ b/drivers/gpu/drm/xe/xe_i2c.c
> @@ -324,8 +324,10 @@ void xe_i2c_pm_resume(struct xe_device *xe, bool d3cold)
>  static void xe_i2c_remove(void *data)
>  {
>  	struct xe_i2c *i2c = data;
> +	struct xe_device *xe = tile_to_xe(i2c->mmio->tile);
>  	unsigned int i;
>  
> +	xe_i2c_irq_reset(xe);
>  	xe_amc_exit(i2c);
>  
>  	for (i = 0; i < XE_I2C_MAX_CLIENTS; i++) {
> -- 
> 2.43.0

-- 
heikki

  parent reply	other threads:[~2026-09-11 11:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  4:40 [PATCH v1] drm/xe/i2c: Disable IRQ on unbind Raag Jadav
2026-09-11  4:54 ` sashiko-bot
2026-09-11  5:02 ` ✓ CI.KUnit: success for " Patchwork
2026-09-11  5:40 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-11 11:17 ` Heikki Krogerus [this message]
2026-09-11 12:12   ` [PATCH v1] " Raag Jadav
2026-09-11 13:30 ` ✓ Xe.CI.FULL: success for " Patchwork

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=aqPjOgEgFG04B_ef@black.igk.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=raag.jadav@intel.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