From: Joe Korty <joe.korty@ccur.com>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Fix overbroad /proc/timer_list file permissions
Date: Tue, 25 Nov 2008 17:44:39 -0500 [thread overview]
Message-ID: <20081125224439.GA24042@tsunami.ccur.com> (raw)
Fix overbroad file permissions on /proc/timer_list.
/proc/timer_list has 0644 permissions, this should be 0444.
Signed-off-by: Joe Korty <joe.korty@ccur.com>
Index: 2.6.28-rc6/kernel/time/timer_list.c
===================================================================
--- 2.6.28-rc6.orig/kernel/time/timer_list.c 2008-11-25 17:32:46.000000000 -0500
+++ 2.6.28-rc6/kernel/time/timer_list.c 2008-11-25 17:33:16.000000000 -0500
@@ -286,7 +286,7 @@
{
struct proc_dir_entry *pe;
- pe = proc_create("timer_list", 0644, NULL, &timer_list_fops);
+ pe = proc_create("timer_list", 0444, NULL, &timer_list_fops);
if (!pe)
return -ENOMEM;
return 0;
next reply other threads:[~2008-11-25 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 22:44 Joe Korty [this message]
2008-11-25 23:14 ` [PATCH] Add per-cpu indexing to /proc/timer_list Joe Korty
2008-11-26 4:50 ` Alexey Dobriyan
2008-11-26 14:39 ` Joe Korty
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=20081125224439.GA24042@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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