[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260204200034.b1UsoMT9@linutronix.de>
Date: Wed, 4 Feb 2026 21:00:34 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Cosmin-Gabriel Tanislav <cosmin-gabriel.tanislav.xa@...esas.com>
Cc: Geert Uytterhoeven <geert+renesas@...der.be>,
Linus Walleij <linusw@...nel.org>,
Clark Williams <clrkwllms@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Bartosz Golaszewski <brgl@...nel.org>,
"linux-renesas-soc@...r.kernel.org" <linux-renesas-soc@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rt-devel@...ts.linux.dev" <linux-rt-devel@...ts.linux.dev>
Subject: Re: RE: [PATCH] pinctrl: renesas: rzt2h: fix invalid wait context
On 2026-02-04 19:53:36 [+0000], Cosmin-Gabriel Tanislav wrote:
> > From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> > Sent: Wednesday, February 4, 2026 9:14 PM
> >
> > On 2026-02-04 20:04:48 [+0200], Cosmin Tanislav wrote:
> > > The following invalid wait context BUG is observed when running with
> > > CONFIG_PROVE_LOCKING enabled.
> > >
> > > This seems to stem from the fact that __setup_irq() takes a
> > > raw_spinlock_t, while we take a spinlock_t inside gpiod_get_direction().
> >
> > From the backtrace yes. It is more that the irqchip used interrupt chip
> > needs to be able to mask interrupts in hardirq context which it needs a
> > raw_spinlock_t.
> >
>
> Would you like me to reword the commit message? I only analyzed why it
> happens, I didn't investigate why it needs to happen. :D
It did explain. It would make sense to include the reasoning and not
symptoms.
Sebastian
Powered by blists - more mailing lists