From: ebiederm@xmission.com (Eric W. Biederman)
To: David Howells <dhowells@redhat.com>
Cc: torvalds@linux-foundation.org, 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: Thu, 30 Jan 2014 13:48:48 -0800 [thread overview]
Message-ID: <8761p1m98f.fsf@xmission.com> (raw)
In-Reply-To: <20140126122729.32113.19659.stgit@warthog.procyon.org.uk> (David Howells's message of "Sun, 26 Jan 2014 12:27:29 +0000")
David Howells <dhowells@redhat.com> writes:
> From: Pali Rohár <pali.rohar@gmail.com>
>
> Both proc files are writeable and used for configuring cells. But
> there is missing correct mode flag for writeable files. Without
> this patch both proc files are read only.
Dumb question. Is this worth fixing? Should we perhaps instead remove
the write methods?
These files have been read-only since this code was merged in 2002.
Over a decade of not being used seems like a strong indication that no
one cares about the write path.
Eric
> Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
> Signed-off-by: David Howells <dhowells@redhat.com>
> ---
>
> fs/afs/proc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/afs/proc.c b/fs/afs/proc.c
> index 526e4bbbde59..276cb6ed0b93 100644
> --- a/fs/afs/proc.c
> +++ b/fs/afs/proc.c
> @@ -147,11 +147,11 @@ int afs_proc_init(void)
> if (!proc_afs)
> goto error_dir;
>
> - p = proc_create("cells", 0, proc_afs, &afs_proc_cells_fops);
> + p = proc_create("cells", S_IFREG | S_IRUGO | S_IWUSR, proc_afs, &afs_proc_cells_fops);
> if (!p)
> goto error_cells;
>
> - p = proc_create("rootcell", 0, proc_afs, &afs_proc_rootcell_fops);
> + p = proc_create("rootcell", S_IFREG | S_IRUGO | S_IWUSR, proc_afs, &afs_proc_rootcell_fops);
> if (!p)
> goto error_rootcell;
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2014-01-30 21:49 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
2014-01-30 21:48 ` Eric W. Biederman [this message]
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=8761p1m98f.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=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 \
/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