public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Kent Gibson <warthog618@gmail.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: WARNING: fs/proc/generic.c:173 __xlate_proc_name
Date: Sun, 25 Feb 2024 11:13:46 +0100	[thread overview]
Message-ID: <f55f2edc-d612-40c0-9822-7d86a940e44e@gmx.net> (raw)
In-Reply-To: <39fe95cb-aa83-4b8b-8cab-63947a726754@gmx.net>

Hi,

[add lkml and linux-fsdevel]

Am 10.02.24 um 11:06 schrieb Stefan Wahren:
> Hi,
> we are using libgpiod-2.0.1 with Linux 6.1.49 on our Tarragon hardware
> platform. Recently we implemented an application which waits for GPIO
> interrupts and we were able to trigger a warning by naming the owner
> of the GPIO as "R1/S1":
>
> WARNING: CPU: 0 PID: 429 at fs/proc/generic.c:173
> __xlate_proc_name+0x78/0x98 name 'R1/S1'
> CPU: 0 PID: 429 Comm: cb_tarragon_dri Not tainted
> 6.1.49-00019-g9dbc76303a17 #147
> Hardware name: Freescale i.MX6 Ultralite (Device Tree)
> unwind_backtrace from show_stack+0x10/0x14
> show_stack from dump_stack_lvl+0x24/0x2c
> dump_stack_lvl from __warn+0x74/0xbc
> __warn from warn_slowpath_fmt+0xc8/0x120
> warn_slowpath_fmt from __xlate_proc_name+0x78/0x98
> __xlate_proc_name from __proc_create+0x3c/0x284
> __proc_create from _proc_mkdir+0x2c/0x70
> _proc_mkdir from proc_mkdir_data+0x10/0x18
> proc_mkdir_data from register_handler_proc+0xc8/0x118
> register_handler_proc from __setup_irq+0x554/0x664
> __setup_irq from request_threaded_irq+0xac/0x13c
> request_threaded_irq from edge_detector_setup+0xc0/0x1f8
> edge_detector_setup from linereq_create+0x30c/0x384
> linereq_create from vfs_ioctl+0x20/0x38
> vfs_ioctl from sys_ioctl+0xbc/0x8b0
> sys_ioctl from ret_fast_syscall+0x0/0x54
> Exception stack(0xe0b61fa8 to 0xe0b61ff0)
> 1fa0:                   01b019b8 01a9f428 0000000d c250b407 beeae888
> beeae880
> 1fc0: 01b019b8 01a9f428 01af7e40 00000036 beeaeb88 beeaeb80 beeaeb58
> beeaeb60
> 1fe0: 00000036 beeae868 b6a88569 b6a01ae6
> ---[ end trace 0000000000000000 ]---
>
> I'm not sure where this should be fixed.
>
since the discussion seems to stuck here [1], i reposted my original
mail to a wider audience.

Regards

[1] - https://lore.kernel.org/linux-gpio/20240213030409.GA35527@rigel/

  parent reply	other threads:[~2024-02-25 10:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-10 10:06 WARNING: fs/proc/generic.c:173 __xlate_proc_name Stefan Wahren
2024-02-12 10:56 ` Bartosz Golaszewski
2024-02-12 13:34 ` Linus Walleij
2024-02-12 13:46   ` Geert Uytterhoeven
2024-02-12 14:11     ` Bartosz Golaszewski
2024-02-13  3:04       ` Kent Gibson
2024-02-25 10:13 ` Stefan Wahren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-25 10:37 Alexey Dobriyan
2024-02-25 10:47 ` Stefan Wahren
2024-02-25 16:27   ` Alexey Dobriyan

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=f55f2edc-d612-40c0-9822-7d86a940e44e@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=brgl@bgdev.pl \
    --cc=geert@linux-m68k.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warthog618@gmail.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