From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-iio@vger.kernel.org,
William Breathitt Gray <wbg@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
linux-kernel@vger.kernel.org,
"Paul E . McKenney" <paulmck@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] counter: interrupt-cnt: Drop IRQF_NO_THREAD flag
Date: Tue, 18 Nov 2025 11:30:22 +0100 [thread overview]
Message-ID: <20251118103022.1FY-iKhs@linutronix.de> (raw)
In-Reply-To: <20251118083603.778626-1-alexander.sverdlin@siemens.com>
On 2025-11-18 09:35:48 [+0100], A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> An IRQ handler can either be IRQF_NO_THREAD or acquire spinlock_t, as
> CONFIG_PROVE_RAW_LOCK_NESTING warns:
> =============================
> [ BUG: Invalid wait context ]
> 6.18.0-rc1+git... #1
> -----------------------------
> some-user-space-process/1251 is trying to lock:
> (&counter->events_list_lock){....}-{3:3}, at: counter_push_event [counter]
> other info that might help us debug this:
> context-{2:2}
> no locks held by some-user-space-process/....
> stack backtrace:
> CPU: 0 UID: 0 PID: 1251 Comm: some-user-space-process 6.18.0-rc1+git... #1 PREEMPT
> Call trace:
> show_stack (C)
> dump_stack_lvl
> dump_stack
> __lock_acquire
> lock_acquire
> _raw_spin_lock_irqsave
> counter_push_event [counter]
> interrupt_cnt_isr [interrupt_cnt]
> __handle_irq_event_percpu
> handle_irq_event
> handle_simple_irq
> handle_irq_desc
> generic_handle_domain_irq
> gpio_irq_handler
> handle_irq_desc
> generic_handle_domain_irq
> gic_handle_irq
> call_on_irq_stack
> do_interrupt_handler
> el0_interrupt
> __el0_irq_handler_common
> el0t_64_irq_handler
> el0t_64_irq
I would recommend to trim the commit message to what is required in
terms of describing the problem you faced. This backtrace contains a lot
noise and is not relevant.
The problem is that IRQF_NO_THREAD does not allow threading the
interrupt handler. Using spinlock_t in non-threaded (atomic) context is
not allowed and is reported by lockdep.
> ... and Sebastian correctly points out. Remove IRQF_NO_THREAD as an
> alternative to switching to raw_spinlock_t, because the latter would limit
> all potential nested locks to raw_spinlock_t only.
Correct.
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Cc: stable@vger.kernel.org
> Link: https://lore.kernel.org/all/20251117151314.xwLAZrWY@linutronix.de/
> Fixes: a55ebd47f21f ("counter: add IRQ or GPIO based counter")
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Sebastian
next prev parent reply other threads:[~2025-11-18 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 8:35 A. Sverdlin
2025-11-18 9:12 ` Oleksij Rempel
2025-11-18 9:51 ` Sverdlin, Alexander
2025-11-18 9:54 ` Oleksij Rempel
2025-11-18 10:08 ` Sebastian Andrzej Siewior
2025-11-18 10:30 ` Sebastian Andrzej Siewior [this message]
2025-11-30 13:57 ` William Breathitt Gray
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=20251118103022.1FY-iKhs@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.fatoum@pengutronix.de \
--cc=alexander.sverdlin@siemens.com \
--cc=kernel@pengutronix.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=paulmck@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wbg@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
all inboxes | Powered by JetHome®