workqueue: Add the allocation flags to function schedule_on_each_cpu_gfp
PATCH 1/1 workqueue: Add the allocation flags to function schedule_on_each_cpu_gfp
Rename the function schedule_on_each_cpu to schedule_on_each_cpu_gfp to add the allocation flags as parameter.
In several situation in ftrace, we are nervous and never come back, once schedule_on_each_cpu fails to alloc the percpu work. Add the allocation flags __GFP_NOFAIL to guarantee it.
--- arch/x86/platform/uv/uv_time.c | 2 +- include/linux/ftrace.h | 2 +- include/linux/workqueue.h | 2 +- kernel/trace/ftrace.c | 5 +++-- kernel/trace/trace_events.c | 2 +- kernel/workqueue.c | 11 ++++++----- 6 files changed, 13 insertions(+), 11 deletions(-)
arch/x86/platform/uv/uv_time.c +1 -1
@@ -405,7 +405,7 @@ static __init int uv_rtc_setup_clock(void) clock_event_device_uv.max_delta_ns = clocksource_uv.mask * (NSEC_PER_SEC / sn_rtc_cycles_per_second); - rc =schedule_on_each_cpu (uv_rtc_register_clockevents); + rc =schedule_on_each_cpu_gfp (uv_rtc_register_clockevents,GFP_KERNEL );if (rc) { x86_platform_ipi_callback =NULL ;uv_rtc_deallocate_timers ();
include/linux/ftrace.h +1 -1
@@ -154,7 +154,7 @@ struct ftrace_ops_hash {* * Any private data added must also take care not to be freed and if private * data is added to a ftrace_ops that is in core code, the user of the -* ftrace_ops must perform a schedule_on_each_cpu() before freeing it. +* ftrace_ops must perform a schedule_on_each_cpu_gfp() before freeing it. */ struct ftrace_ops {ftrace_func_t func;
include/linux/workqueue.h +1 -1
@@ -436,7 +436,7 @@ extern bool mod_delayed_work_on(int cpu, struct workqueue_struct *wq,extern void flush_workqueue (struct workqueue_struct *wq);extern void drain_workqueue (struct workqueue_struct *wq); -extern int schedule_on_each_cpu (work_func_t func); +extern int schedule_on_each_cpu_gfp (work_func_t func,gfp_t gfp);int execute_in_process_context (work_func_t fn,struct execute_work *);
kernel/trace/ftrace.c +3 -2
@@ -324,7 +324,7 @@ static void update_ftrace_function(void)* Make sure all CPUs see this. Yes this is slow, but static * tracing is slow and nasty to have enabled. */ -schedule_on_each_cpu (ftrace_sync); +schedule_on_each_cpu_gfp (ftrace_sync,GFP_KERNEL | __GFP_NOFAIL);/* Now all cpus are using the list ops. */ function_trace_op = set_function_trace_op;/* Make sure the function_trace_op is visible on all CPUs */
@@ -2716,7 +2716,8 @@ static int ftrace_shutdown(struct ftrace_ops *ops, int command)* ourselves. */ if (ops->flags & (FTRACE_OPS_FL_DYNAMIC |FTRACE_OPS_FL_CONTROL )) { -schedule_on_each_cpu (ftrace_sync); +schedule_on_each_cpu_gfp (ftrace_sync, +GFP_KERNEL | __GFP_NOFAIL);arch_ftrace_trampoline_free (ops);
kernel/trace/trace_events.c +1 -1
@@ -2722,7 +2722,7 @@ static __init int event_test_thread(void *unused)if (!test_malloc)pr_info ("failed to kmalloc\n" ); -schedule_on_each_cpu (test_work); +schedule_on_each_cpu_gfp (test_work,GFP_KERNEL );kfree (test_malloc);
kernel/workqueue.c +6 -5
@@ -2917,22 +2917,23 @@ bool cancel_delayed_work_sync(struct delayed_work *dwork)EXPORT_SYMBOL (cancel_delayed_work_sync);/** -* schedule_on_each_cpu - execute a function synchronously on each online CPU +* schedule_on_each_cpu_gfp - execute function synchronously on each online CPU * @func: the function to call +* @gfp: allocation flags * -* schedule_on_each_cpu() executes @func on each online CPU using the +* schedule_on_each_cpu_gfp() executes @func on each online CPU using the * system workqueue and blocks until all CPUs have completed. -* schedule_on_each_cpu() is very slow. +* schedule_on_each_cpu_gfp() is very slow. * * Return: * 0 on success, -errno on failure. */ -int schedule_on_each_cpu (work_func_t func) +int schedule_on_each_cpu_gfp (work_func_t func,gfp_t gfp) {int cpu;struct work_struct __percpu *works; - works = alloc_percpu(struct work_struct); + works = alloc_percpu_gfp(struct work_struct, gfp);if (!works)return -ENOMEM ;
Signature · 1 line
2.4.0
Quoted 136 lines · Minfei Huang
Rename the function
schedule_on_each_cputoschedule_on_each_cpu_gfpto add the allocation flags as parameter.In several situation in ftrace, we are nervous and never come back, once
schedule_on_each_cpufails to alloc the percpu work. Add the allocation flags__GFP_NOFAILto guarantee it.Signed-off-by Minfei Huang <[email protected]>---
arch/x86/platform/uv/uv_time.c | 2 +- include/linux/ftrace.h | 2 +- include/linux/workqueue.h | 2 +- kernel/trace/ftrace.c | 5 +++-- kernel/trace/trace_events.c | 2 +- kernel/workqueue.c | 11 ++++++----- 6 files changed, 13 insertions(+), 11 deletions(-)arch/x86/platform/uv/uv_time.c +1
-1@@ -405,7 +405,7 @@ static __init int uv_rtc_setup_clock(void) clock_event_device_uv.max_delta_ns = clocksource_uv.mask * (NSEC_PER_SEC / sn_rtc_cycles_per_second); - rc =schedule_on_each_cpu (uv_rtc_register_clockevents); + rc =schedule_on_each_cpu_gfp (uv_rtc_register_clockevents,GFP_KERNEL );if (rc) { x86_platform_ipi_callback =NULL ;uv_rtc_deallocate_timers ();include/linux/ftrace.h +1
-1@@ -154,7 +154,7 @@ struct ftrace_ops_hash {* * Any private data added must also take care not to be freed and if private * data is added to a ftrace_ops that is in core code, the user of the -* ftrace_ops must perform a schedule_on_each_cpu() before freeing it. +* ftrace_ops must perform a schedule_on_each_cpu_gfp() before freeing it. */ struct ftrace_ops {ftrace_func_t func;include/linux/workqueue.h +1
-1@@ -436,7 +436,7 @@ extern bool mod_delayed_work_on(int cpu, struct workqueue_struct *wq,extern void flush_workqueue (struct workqueue_struct *wq);extern void drain_workqueue (struct workqueue_struct *wq); -extern int schedule_on_each_cpu (work_func_t func); +extern int schedule_on_each_cpu_gfp (work_func_t func,gfp_t gfp);int execute_in_process_context (work_func_t fn,struct execute_work *);kernel/trace/ftrace.c +3
-2@@ -324,7 +324,7 @@ static void update_ftrace_function(void)* Make sure all CPUs see this. Yes this is slow, but static * tracing is slow and nasty to have enabled. */ -schedule_on_each_cpu (ftrace_sync); +schedule_on_each_cpu_gfp (ftrace_sync,GFP_KERNEL | __GFP_NOFAIL);/* Now all cpus are using the list ops. */ function_trace_op = set_function_trace_op;/* Make sure the function_trace_op is visible on all CPUs */ @@ -2716,7 +2716,8 @@ static int ftrace_shutdown(struct ftrace_ops *ops, int command)* ourselves. */ if (ops->flags & (FTRACE_OPS_FL_DYNAMIC |FTRACE_OPS_FL_CONTROL )) { -schedule_on_each_cpu (ftrace_sync); +schedule_on_each_cpu_gfp (ftrace_sync, +GFP_KERNEL | __GFP_NOFAIL);arch_ftrace_trampoline_free (ops);kernel/trace/trace_events.c +1
-1@@ -2722,7 +2722,7 @@ static __init int event_test_thread(void *unused)if (!test_malloc)pr_info ("failed to kmalloc\n" ); -schedule_on_each_cpu (test_work); +schedule_on_each_cpu_gfp (test_work,GFP_KERNEL );kfree (test_malloc);kernel/workqueue.c +6
-5@@ -2917,22 +2917,23 @@ bool cancel_delayed_work_sync(struct delayed_work *dwork)EXPORT_SYMBOL (cancel_delayed_work_sync);/** -* schedule_on_each_cpu - execute a function synchronously on each online CPU +* schedule_on_each_cpu_gfp - execute function synchronously on each online CPU * @func: the function to call +* @gfp: allocation flags * -* schedule_on_each_cpu() executes @func on each online CPU using the +* schedule_on_each_cpu_gfp() executes @func on each online CPU using the * system workqueue and blocks until all CPUs have completed. -* schedule_on_each_cpu() is very slow. +* schedule_on_each_cpu_gfp() is very slow. * * Return: * 0 on success, -errno on failure. */ -int schedule_on_each_cpu (work_func_t func) +int schedule_on_each_cpu_gfp (work_func_t func,gfp_t gfp) {int cpu;struct work_struct __percpu *works; - works = alloc_percpu(struct work_struct); + works = alloc_percpu_gfp(struct work_struct, gfp);if (!works)return -ENOMEM ;Signature · 7 lines
2.4.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
better to also provide a wrapper function with name schedule_on_each_cpu(), as this function is used frequently .
#define schedule_on_each_cpu(f) schedule_on_each_cpu_gfp(f, GFP_KERNEL)
Thanks
Steven Rostedt
maintainerQuoted 4 lines · On Mon, 3 Aug 2015 17:15:53 +0800 yalin wang <[email protected]> wrote:
better to also provide a wrapper function with name
schedule_on_each_cpu(), as this function is used frequently .#define
schedule_on_each_cpu(f)schedule_on_each_cpu_gfp(f, GFP_KERNEL)
I was about to say pretty much the same thing. But please make it an inline function:
static inline int schedule_on_each_cpu(work_func_t func)
{
return schedule_on_each_cpu_gfp(func, GFP_KERNEL);
}Otherwise, NACK to the patch to the ftrace code.
-- Steve
Quoted 11 lines · Steven Rostedt
Quoted 4 lines · On Mon, 3 Aug 2015 17:15:53 +0800 yalin wang <[email protected]> wrote:
better to also provide a wrapper function with name
schedule_on_each_cpu(), as this function is used frequently .#define
schedule_on_each_cpu(f)schedule_on_each_cpu_gfp(f, GFP_KERNEL)I was about to say pretty much the same thing. But please make it an inline function:
Quoted 6 lines
static inline int
schedule_on_each_cpu(work_func_t func){ return schedule_on_each_cpu_gfp(func, GFP_KERNEL); }Otherwise, NACK to the patch to the ftrace code.
Hi, Steve.
The main reason I posted this patch is to fix the data race bug, when ftrace tries to free the ops->trampoline in arch x86.
Function schedule_on_each_cpu may fail to alloc percpu work to synchronise each online cpu. In such situation, trying to free the trampoline may casue the kernel crash, because one cpu may be executing the trampoline at this moment.
So I add a new wrapper function to fix it.
Thanks
Minfei
Tejun Heo
maintainerQuoted 6 lines · Minfei Huang
Rename the function
schedule_on_each_cputoschedule_on_each_cpu_gfpto add the allocation flags as parameter.In several situation in ftrace, we are nervous and never come back, once
schedule_on_each_cpufails to alloc the percpu work. Add the allocation flags__GFP_NOFAILto guarantee it.
I don't know the context well here but new usages of __GFP_NOFAIL are strongly frowned upon. __GFP_NOFAIL was introduced to replace explicit infinite allocation loops and its main purpose is marking "this site is broken and a deadlock possibility, somebody please figure out how to fix it". After all, retrying over and over again can't possibly guarantee to create more memory. Maybe the constant should be renamed to something more vulgar.
So, please reconsider.
Thanks.
Signature · 1 line
tejun