Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-i2c@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	Waiman Long <longman@redhat.com>,
	linux-rt-devel@lists.linux.dev,
	Andi Shyti <andi.shyti@kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>
Subject: Re: [BUG] exynos5_i2c_xfer_atomic() can sleep.
Date: Fri, 8 May 2026 12:09:10 +0200	[thread overview]
Message-ID: <20260508100910.nxRkt3mA@linutronix.de> (raw)
In-Reply-To: <03c06142-12eb-45b7-8d22-ce12fab6e132@samsung.com>

On 2026-05-08 11:45:15 [+0200], Marek Szyprowski wrote:
> On 06.05.2026 08:51, Sebastian Andrzej Siewior wrote:
> > While looking into the xfer_atomic i2c thingy, I've been looking at the
> > exynos5_i2c_xfer_atomic() function and noticed that it has a
> > disable_irq() invocation. Given that i2c_algorithm::xfer_atomic is
> > called from atomic context (with either preemption or interrupts
> > disabled) the might_sleep() in disable_irq() must lead to splat here.
> 
> Its me, who added that code, commit 445094c8a9fb1. I've tested that in
> the reboot/shutdown path and I'm quite sure that I've copied that
> irq_disable/enable from some other driver. I also cannot locate that
> might_sleep() in disable_irq(), where exactly it is?

kernel/irq/manage.c:
| void disable_irq(unsigned int irq)
| {
|         might_sleep();
|         if (!__disable_irq_nosync(irq))
^^
|                 synchronize_irq(irq);
| }
| EXPORT_SYMBOL(disable_irq);

Sebastian

  reply	other threads:[~2026-05-08 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20260506065541eucas1p2f986355d0a06ac1f72aa00e8d3148ad0@eucas1p2.samsung.com>
2026-05-06  6:51 ` [BUG] exynos5_i2c_xfer_atomic() can sleep Sebastian Andrzej Siewior
2026-05-08  9:45   ` Marek Szyprowski
2026-05-08 10:09     ` Sebastian Andrzej Siewior [this message]
2026-05-08 10:35       ` Marek Szyprowski
2026-05-08 10:42         ` Sebastian Andrzej Siewior
2026-05-08 15:28           ` Marek Szyprowski
2026-05-08 15:52             ` Sebastian Andrzej Siewior

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=20260508100910.nxRkt3mA@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=alim.akhtar@samsung.com \
    --cc=andi.shyti@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=m.szyprowski@samsung.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