From: Amerigo Wang <amwang@redhat.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Vegard Nossum <vegard.nossum@gmail.com>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Thomas Gleixner <tglx@linutronix.de>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Matt Mackall <mpm@selenic.com>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [Patch] proc: drop write permission on 'timer_list' and 'slabinfo'
Date: Tue, 18 Aug 2009 09:59:41 +0800 [thread overview]
Message-ID: <4A8A0B0D.6080400@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0908171240370.16267@gentwo.org>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Christoph Lameter wrote:
> On Mon, 17 Aug 2009, Pekka Enberg wrote:
>
>
>>> slab needs the write permissions for tuning!
>>>
>> Oh, crap, you're right, I had forgotten about that. It's probably best to keep
>> slub permissions as-is, no?
>>
Oops! I misread the code... sorry.
>
> slub perms can be changed. The patch is okay for that. But there is no
> write method in slub. Effectively it makes no difference. Just the
> display is nicer in /proc.
>
>
>
Ah, ok, I update this part of patch, attached.
Thanks!
Signed-off-by: WANG Cong <amwang@redhat.com>
[-- Attachment #2: proc-file-write-permission-fix2.diff --]
[-- Type: text/plain, Size: 422 bytes --]
diff --git a/mm/slub.c b/mm/slub.c
index b9f1491..aba2c1b 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -4726,7 +4726,7 @@ static const struct file_operations proc_slabinfo_operations = {
static int __init slab_proc_init(void)
{
- proc_create("slabinfo",S_IWUSR|S_IRUGO,NULL,&proc_slabinfo_operations);
+ proc_create("slabinfo",S_IRUSR|S_IRUGO,NULL,&proc_slabinfo_operations);
return 0;
}
module_init(slab_proc_init);
next prev parent reply other threads:[~2009-08-18 1:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 9:43 Amerigo Wang
2009-08-17 9:48 ` Ingo Molnar
2009-08-17 9:54 ` Pekka Enberg
2009-08-17 16:29 ` Christoph Lameter
2009-08-17 16:35 ` Pekka Enberg
2009-08-17 16:41 ` Christoph Lameter
2009-08-18 1:59 ` Amerigo Wang [this message]
2009-08-18 1:59 ` Li Zefan
2009-08-18 3:08 ` Amerigo Wang
2009-08-18 12:00 ` Wu Fengguang
2009-08-19 2:36 ` Amerigo Wang
2009-08-19 2:37 ` Wu Fengguang
2009-08-19 10:39 ` Amerigo Wang
2009-08-19 18:47 ` Pekka Enberg
2009-08-20 10:34 ` Amerigo Wang
2009-08-18 16:12 ` Pekka Enberg
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=4A8A0B0D.6080400@redhat.com \
--to=amwang@redhat.com \
--cc=arjan@linux.intel.com \
--cc=cl@linux-foundation.org \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.com \
/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