From: Andrew Morton <akpm@osdl.org>
To: Nathan Lynch <nathanl@austin.ibm.com>
Cc: olh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] prohibit slash in proc directory entry names
Date: Wed, 5 Jan 2005 16:07:04 -0800 [thread overview]
Message-ID: <20050105160704.7dc36ca4.akpm@osdl.org> (raw)
In-Reply-To: <1104952961.10796.41.camel@pants.austin.ibm.com>
Nathan Lynch <nathanl@austin.ibm.com> wrote:
>
> proc_create() needs to check that the name of an entry to be created
> does not contain a '/' character.
>
> To test, I hacked the ibmveth driver to try to call request_irq with a
> bogus "foo/bar" devname. The creation of the /proc/irq/1234/xxx entry
> silently fails, as intended. Perhaps the irq code should be made to
> check for the failure.
>
> Signed-off-by: Nathan Lynch <nathanl@austin.ibm.com>
>
> Index: 2.6.10/fs/proc/generic.c
> ===================================================================
> --- 2.6.10.orig/fs/proc/generic.c 2004-12-24 21:35:40.000000000 +0000
> +++ 2.6.10/fs/proc/generic.c 2005-01-05 18:44:56.000000000 +0000
> @@ -551,6 +551,11 @@
>
> if (!(*parent) && xlate_proc_name(name, parent, &fn) != 0)
> goto out;
> +
> + /* At this point there must not be any '/' characters beyond *fn */
> + if (strchr(fn, '/'))
> + goto out;
> +
hm. From a brief code-squint I don't see how the string can ever have a
slash in it by this stage. Unless the caller provided a non-null *parent
and we never called xlate_proc_name()?
next prev parent reply other threads:[~2005-01-06 0:07 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
2005-01-05 19:22 ` [PATCH] prohibit slash in proc directory entry names Nathan Lynch
2005-01-06 0:07 ` Andrew Morton [this message]
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=20050105160704.7dc36ca4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.ibm.com \
--cc=olh@suse.de \
/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