linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] request_irq: avoid slash in proc directory entries
Date: Wed, 5 Jan 2005 10:34:57 +0100	[thread overview]
Message-ID: <20050105093457.GA8684@suse.de> (raw)
In-Reply-To: <20050105000129.63478670.akpm@osdl.org>

 On Wed, Jan 05, Andrew Morton wrote:

> Olaf Hering <olh@suse.de> wrote:
> >
> > A few users of request_irq pass a string with '/'.
> >  As a result, ls -l /proc/irq/*/* will fail to list these entries.
> 
> hrm, interesting.  So how do these entries appear in /proc?  Do they
> actually have slashes in them?

Yes, ls /proc/irq/*/* works, but ls -l does not because you have to
stat() the entry. I havent looked in detail, just poked around in /proc.

> I get the feeling that something somewhere should be detecting this and
> should be propagating an error back.

Yeah, a quick sanity check for procfile creation would be a good thing.

  reply	other threads:[~2005-01-05  9:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05  7:53 [PATCH] request_irq: avoid slash in proc directory entries Olaf Hering
2005-01-05  8:01 ` Andrew Morton
2005-01-05  9:34   ` Olaf Hering [this message]
2005-01-05 19:22   ` [PATCH] prohibit slash in proc directory entry names Nathan Lynch
2005-01-06  0:07     ` Andrew Morton
2005-01-06  0:12       ` Nathan Lynch
2005-01-05 12:37 ` [PATCH] request_irq: avoid slash in proc directory entries Alan Cox
2005-01-05 13:53   ` Olaf Hering

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=20050105093457.GA8684@suse.de \
    --to=olh@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).