Re: RT patch breaks X86_64 build

Hi Ingo,

I don't see why /proc/sys/kernel/preempt_{max_latency,thresh} should not be readable for all users. They already can see much more detailed information in /proc/latency_trace.

Michal

--- linux-RT.mich/kernel/latency.c.orig	2005-06-02 13:42:23.000000000 +0200
+++ linux-RT.mich/kernel/latency.c	2005-06-02 12:57:05.000000000 +0200
@@ -1809,14 +1809,14 @@ static __init int latency_init(void)
 {
 	struct proc_dir_entry *entry;
 
-	entry = create_proc_entry("sys/kernel/preempt_max_latency", 0600, NULL);
+	entry = create_proc_entry("sys/kernel/preempt_max_latency", 0644, NULL);
 
 	entry->nlink = 1;
 	entry->data = &preempt_max_latency;
 	entry->read_proc = preempt_read_proc;
 	entry->write_proc = preempt_write_proc;
 
-	entry = create_proc_entry("sys/kernel/preempt_thresh", 0600, NULL);
+	entry = create_proc_entry("sys/kernel/preempt_thresh", 0644, NULL);
 
 	entry->nlink = 1;
 	entry->data = &preempt_thresh;

---

• Follow-Ups:
  • Re: RT patch breaks X86_64 build
    • From: Ingo Molnar <[email protected]>

• References:
  • RT patch breaks X86_64 build
    • From: Parag Warudkar <[email protected]>
  • Re: RT patch breaks X86_64 build
    • From: Parag Warudkar <[email protected]>
  • Re: RT patch breaks X86_64 build
    • From: Michal Schmidt <[email protected]>
  • Re: RT patch breaks X86_64 build
    • From: Parag Warudkar <[email protected]>
  • Re: RT patch breaks X86_64 build
    • From: Ingo Molnar <[email protected]>

• Prev by Date: Re: [PATCH 1/3] eCryptfs: eCryptfs kernel module
• Next by Date: Re: [PATCH 1/3] eCryptfs: eCryptfs kernel module
• Previous by thread: Re: RT patch breaks X86_64 build
• Next by thread: Re: RT patch breaks X86_64 build
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]