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: <36cace3b-7419-409d-95a9-e7c45d335bef@molgen.mpg.de>
Date: Fri, 21 Feb 2025 22:02:03 +0100
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
 Linus Walleij <linus.walleij@...aro.org>, linux-gpio@...r.kernel.org,
 LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org,
 regressions@...ts.linux.dev
Subject: Re: Linux logs new warning `gpio gpiochip0:
 gpiochip_add_data_with_key: get_direction failed: -22`

Dear Bartosz,


Thank you for your quick reply.

Am 21.02.25 um 21:53 schrieb Bartosz Golaszewski:
> On Fri, Feb 21, 2025 at 9:40 PM Paul Menzel <pmenzel@...gen.mpg.de> wrote:

>> On the Intel Kaby Lake Dell XPS 13 9360, Linux 6.14-rc3+ with your
>> commit 9d846b1aebbe (gpiolib: check the return value of
>> gpio_chip::get_direction()) prints 52 new warnings:
>>
>>       $ dmesg
>>       […]
>>       [    0.000000] DMI: Dell Inc. XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022
>>       […]
>>       [    5.148927] pci 0000:00:1d.0: PCI bridge to [bus 3c]
>>       [    5.150955] gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22
>>       [50 times the same]
>>       [    5.151639] gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22
>>       [    5.151768] ACPI: PCI: Interrupt link LNKA configured for IRQ 11
>>       […]
>>       $ lspci -nn -k -s 1d.0
>>       00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1)
>>          Subsystem: Dell Device [1028:075b]
>>          Kernel driver in use: pcieport
>>
>> Judging from the commit messages, this is expected. But what should a
>> user seeing this do now?
>>
>> Also, it probably should not be applied to the stable series, as people
>> might monitor warnings and new warnings in stable series might be
>> unexpected.


>> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9d846b1aebbe488f245f1aa463802ff9c34cc078

> What GPIO driver is it using? It's likely that it's not using the
> provider API correctly and this change uncovered it, I'd like to take
> a look at it and fix it.

How do I find out? The commands below do not return anything.

     $ lsmod | grep gpio
     $ lspci -nn | grep -i gpio
     $ sudo dmesg | grep gpio
     [    5.150955] gpio gpiochip0: gpiochip_add_data_with_key: 
get_direction failed: -22
     [Just these lines match.]


Kind regards,

Paul

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ