[PATCH] ftrace: The set_graph_function and set_graph_notrace file mode should be 0644 instead of 0444

2014-09-03 Thread Chen LinX
Signed-off-by: Chen LinX --- kernel/trace/ftrace.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c index 5916a8e..00e7b9a 100644 --- a/kernel/trace/ftrace.c +++ b/kernel/trace/ftrace.c @@ -4406,10 +4406,10 @@ static __init int

[PATCH] ftrace: The set_graph_function and set_graph_notrace file mode should be 0644 instead of 0444

2014-09-03 Thread Chen LinX
Signed-off-by: Chen LinX linx.z.c...@intel.com --- kernel/trace/ftrace.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c index 5916a8e..00e7b9a 100644 --- a/kernel/trace/ftrace.c +++ b/kernel/trace/ftrace.c @@ -4406,10 +4406,10

[PATCH V2] debugfs: keep the old mode value at remount when no explicit change

2014-08-28 Thread Chen LinX
From: "Chen, LinX" Android framework has a good method to detect userspace hang and reports UIWDT issues. It uses client/server model. Clients communicate with servers by binder. binder has debugfs interfaces. Some files show what threads are communicating with what other threads. If

[PATCH] debugfs: keep the old valid mode value when no explicity specify it

2014-08-28 Thread Chen LinX
From: "Chen, LinX" When mount debugfs with no mode specifed after it's mounted, the mount point mode will change to default mode(0700) even the mount operation was fail, this will cause some issues like can't get binder info in android. Here we can keep the old valid mode if no explici

[PATCH] debugfs: keep the old valid mode value when no explicity specify it

2014-08-28 Thread Chen LinX
From: Chen, LinX linx.z.c...@intel.com When mount debugfs with no mode specifed after it's mounted, the mount point mode will change to default mode(0700) even the mount operation was fail, this will cause some issues like can't get binder info in android. Here we can keep the old valid mode

[PATCH V2] debugfs: keep the old mode value at remount when no explicit change

2014-08-28 Thread Chen LinX
From: Chen, LinX linx.z.c...@intel.com Android framework has a good method to detect userspace hang and reports UIWDT issues. It uses client/server model. Clients communicate with servers by binder. binder has debugfs interfaces. Some files show what threads are communicating with what other

[PATCH V2] perf: Don't enable the perf_event without in PERF_ATTACH_CONTEXT status

2014-07-16 Thread Chen LinX
From: "Chen LinX" ChangeLog V2: 1) Add more description about the race; 2) Format the email to use short lines. When we run cpu hotplug test and below perf test at the same time, kernel panic. pmu may access freed perf_event. while true; do perf re

[PATCH V2] perf: Don't enable the perf_event without in PERF_ATTACH_CONTEXT status

2014-07-16 Thread Chen LinX
From: Chen LinX linx.z.c...@intel.com ChangeLog V2: 1) Add more description about the race; 2) Format the email to use short lines. When we run cpu hotplug test and below perf test at the same time, kernel panic. pmu may access freed perf_event. while true; do

[PATCH] perf: Don't enable the perf_event without in PERF_ATTACH_CONTEXT status

2014-07-02 Thread Chen LinX
From: "Chen LinX" when do cpu hotplug test and run below perf test together, pmu may access freed perf_event while true; do perf record -a -g -f sleep 10 rm perf.* done the scenario is that when cpu offline firstly, the 'perf_cpu_notify' will disable event on the pmu and remo

[PATCH] perf: Don't enable the perf_event without in PERF_ATTACH_CONTEXT status

2014-07-02 Thread Chen LinX
From: Chen LinX linx.z.c...@intel.com when do cpu hotplug test and run below perf test together, pmu may access freed perf_event while true; do perf record -a -g -f sleep 10 rm perf.* done the scenario is that when cpu offline firstly, the 'perf_cpu_notify' will disable event on the pmu

[PATCH V2] x86/smp: Fix cpuN startup panic

2012-08-12 Thread Chen, LinX Z
cause AP busy wait for it. At present, AP will wait for 2 seconds then panic. This patch let AP waits for 60 seconds at maximum. Signed-off-by: Yanmin Zhang Signed-off-by: Chen LinX --- arch/x86/kernel/smpboot.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/ke

[PATCH V2] x86/smp: Fix cpuN startup panic

2012-08-12 Thread Chen, LinX Z
for it. At present, AP will wait for 2 seconds then panic. This patch let AP waits for 60 seconds at maximum. Signed-off-by: Yanmin Zhang yanmin_zh...@linux.intel.com Signed-off-by: Chen LinX linx.z.c...@intel.com --- arch/x86/kernel/smpboot.c |4 ++-- 1 files changed, 2 insertions(+), 2

[PATCH] x86/smp: Fix cpuN startup panic

2012-08-07 Thread Chen, LinX Z
From: Lin Chen We hit a panic while doing cpu hotplug test. <0>[ 627.982857] Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout! <0>[ 627.982864] <4>[ 627.982876] Pid: 0, comm: kworker/0:1 Tainted: G ... <4>[ 627.982883] Call Trace: <4>[ 627.982903] []

[PATCH] x86/smp: Fix cpuN startup panic

2012-08-07 Thread Chen, LinX Z
From: Lin Chen linx.z.c...@intel.com We hit a panic while doing cpu hotplug test. 0[ 627.982857] Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout! 0[ 627.982864] 4[ 627.982876] Pid: 0, comm: kworker/0:1 Tainted: G ... 4[ 627.982883] Call Trace: 4[