linux-kernel - Re: [PATCH] pinctrl: qcom: lpass-lpi: mark the GPIO controller as sleeping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <m7kk4bcmaft6at7isv7p5whvcqrfpydx2ajhp5hzi47m46rzds@gjomcts7c74v>
Date: Wed, 26 Nov 2025 16:40:29 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bjorn Andersson <andersson@...nel.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Srinivas Kandagatla <srini@...nel.org>, linux-arm-msm@...r.kernel.org,
        linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
        Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
        stable@...r.kernel.org, Val Packett <val@...kett.cool>
Subject: Re: [PATCH] pinctrl: qcom: lpass-lpi: mark the GPIO controller as
 sleeping

On Wed, Nov 26, 2025 at 01:22:19PM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> 
> The gpio_chip settings in this driver say the controller can't sleep
> but it actually uses a mutex for synchronization. This triggers the
> following BUG():
> 
> [    9.233659] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:281

Nit: usually you can strip timestamps from the kernel dump.

Other than that:

Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>


> [    9.233665] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 554, name: (udev-worker)

-- 
With best wishes
Dmitry