mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Myeonghun Pak <mhun512@gmail.com>
Cc: wsa+renesas@sang-engineering.com,
	linux-renesas-soc@vger.kernel.org,  linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, ae878000@gmail.com
Subject: Re: [PATCH] i2c: sh_mobile: request IRQs after mapping registers
Date: Sat, 24 Oct 2026 00:09:26 +0200	[thread overview]
Message-ID: <atvUWb-PzouZzL5D@zenone.zhora.eu> (raw)
In-Reply-To: <20261017233416.47b09ffff48f.i2c-sh-mobile@gmail.com>

Hi Myeounghun,

On Sat, Oct 17, 2026 at 11:35:16PM -0400, Myeonghun Pak wrote:
> The managed IRQ handlers are acquired before the managed register
> mapping, so devres unmaps the registers before freeing the IRQs. A
> transfer wakes its waiter before the ISR's final register read, and
> unregistering the adapter does not synchronize these IRQs. An in-flight
> handler can therefore still access the mapping when it is released
> during driver detach.
> 
> With forced-threaded IRQs, the handler can be preempted after waking the
> transfer waiter and before its final ICSR read.
> 
> Map the registers before requesting the IRQs so that managed cleanup
> frees and synchronizes all handlers before unmapping their registers.
> Keep IRQs available while unregistering the adapter because client
> removal may perform transfers.
> 
> This issue was identified as part of our ongoing research while
> reviewing kernel code.
> 
> Fixes: 7fe8a9993337 ("i2c: sh_mobile: devm conversion, irq setup")

Normally, I don't like taking fixes that don't address real
issues, especially speculative AI-generated fixes.

However, this looks like a harmless reordering that seems
correct, although the issue it addresses is rather
hypothetical.

I'll remove the Fixes: tag, since this is purely speculative,
and apply the patch to i2c/i2c.

Thanks,
Andi

  reply	other threads:[~2026-10-23 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18  3:35 Myeonghun Pak
2026-10-23 22:09 ` Andi Shyti [this message]
2026-10-26  8:41   ` Geert Uytterhoeven
2026-11-04 13:09 ` Wolfram Sang
2026-11-04 13:21   ` Wolfram Sang

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=atvUWb-PzouZzL5D@zenone.zhora.eu \
    --to=andi.shyti@kernel.org \
    --cc=ae878000@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mhun512@gmail.com \
    --cc=wsa+renesas@sang-engineering.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®