From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Walleij <linus.walleij@linaro.org>,
Stefan Wahren <wahrenst@gmx.net>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: WARNING: fs/proc/generic.c:173 __xlate_proc_name
Date: Tue, 13 Feb 2024 11:04:09 +0800 [thread overview]
Message-ID: <20240213030409.GA35527@rigel> (raw)
In-Reply-To: <CAMRc=McSdtnqLWrRHoi=6bAuUWfvGqnB+B9FavDDrMfH2vbCkw@mail.gmail.com>
On Mon, Feb 12, 2024 at 03:11:43PM +0100, Bartosz Golaszewski wrote:
> On Mon, Feb 12, 2024 at 2:47 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
...
> > > >
> > > > I'm not sure where this should be fixed.
> >
> > Any names ending up in sysfs cannot contain a slash?
>
> It's actually procfs. Every irq has an entry under /proc/irq/xyz/
> containing a directory named after the name of the interrupt. In this
> case the path of the directory would have been /proc/irq/xyz/R1/S1 but
> of course this wouldn't work. Should we replace every `/` in GPIO line
> names with `:` for interrupts?
>
Agreed that the consumer label (not the GPIO name, btw), needs to be
sanitized before being used to create the procfs path, what I am uncertain
about is whether that should be performed in cdev, irq or even procfs.
If cdev then I would also like to see irq document that the devname cannot
contain slashes - it currently only states:
* @devname: An ascii name for the claiming device
Sanitizing with ":" works for me.
Cheers,
Kent.
next prev parent reply other threads:[~2024-02-13 3:04 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 [this message]
2024-02-25 10:13 ` Stefan Wahren
-- 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=20240213030409.GA35527@rigel \
--to=warthog618@gmail.com \
--cc=brgl@bgdev.pl \
--cc=geert@linux-m68k.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=wahrenst@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.