From: David Howells <dhowells@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: dhowells@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-afs@lists.infradead.org, Pali Roh??r <pali.rohar@gmail.com>
Subject: Re: [PATCH] afs: proc cells and rootcell are writeable
Date: Tue, 28 Jan 2014 20:56:44 +0000 [thread overview]
Message-ID: <28052.1390942604@warthog.procyon.org.uk> (raw)
In-Reply-To: <20140128202754.GI10323@ZenIV.linux.org.uk>
Al Viro <viro@ZenIV.linux.org.uk> wrote:
> > ... and then making proc_create() only permit regular files (and complain
> > if the S_IFMT field is not zero)?
>
> We already do: in proc_create_data() we have
> struct proc_dir_entry *pde;
> if ((mode & S_IFMT) == 0)
> mode |= S_IFREG;
>
> if (!S_ISREG(mode)) {
> WARN_ON(1); /* use proc_mkdir() */
> return NULL;
> }
>
> proc_mkdir{,_data,_mode} are there for purpose. Nobody had been insane
> enough to put FIFOs or sockets in procfs and anything else would need
> additional data anyway. proc_symlink() is there, proc_mknod() isn't and
> nobody has complained yet. Let's keep it that way, plese...
Should we then change the proc_create_data() to do:
struct proc_dir_entry *pde;
if (mode & S_IFMT) {
WARN_ON(1); /* use proc_mkdir() */
return NULL;
}
mode |= S_IFREG;
and stop passing S_IFREG into it?
David
next prev parent reply other threads:[~2014-01-28 20:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 12:27 David Howells
2014-01-26 19:23 ` Linus Torvalds
2014-01-26 20:19 ` Ingo Molnar
2014-01-26 20:22 ` Ingo Molnar
2014-01-26 20:25 ` Ingo Molnar
2014-01-28 8:39 ` Geert Uytterhoeven
2014-01-28 12:04 ` Ingo Molnar
2014-01-28 12:17 ` Geert Uytterhoeven
2014-01-28 12:20 ` Ingo Molnar
2014-01-28 17:34 ` Joe Perches
2014-01-28 20:20 ` David Howells
2014-01-28 20:27 ` Al Viro
2014-01-28 20:56 ` David Howells [this message]
2014-01-30 21:48 ` Eric W. Biederman
2014-01-30 21:50 ` Linus Torvalds
2014-01-30 22:15 ` Pali Rohár
2014-01-30 22:27 ` Linus Torvalds
2014-01-30 22:36 ` Dave Jones
2014-01-30 22:33 ` Russ Allbery
2014-01-31 0:21 ` David Howells
2014-01-31 0:28 ` David Howells
2014-01-31 0:31 ` David Howells
2014-01-31 0:07 ` David Howells
2014-01-31 0:20 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2014-01-27 12:33 Alexey Dobriyan
2013-11-20 13:30 Pali Rohár
2013-12-10 8:02 ` Pali Rohár
2013-12-16 7:00 ` Andrew Morton
2013-12-17 13:19 ` Pali Rohár
2013-12-17 18:31 ` David Howells
2013-12-31 9:59 ` Pali Rohár
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=28052.1390942604@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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
Powered by JetHome