tracing: Some very old (and some new) patches for 5.6
Steven Rostedt
maintainercover tracing: Some very old (and some new) patches for 5.6
Dan Carpenter (1):
tracing: Remove unneeded NULL check
Hou Pengyang (1):
tracing: Fix comments about trace/ftrace.h
Josef Bacik (1):
tracing: Set kernel_stack's caller size properly
Luis Henriques (1):
tracing: Fix tracing_stat return values in error handling paths
Steven Rostedt (VMware) (3):
tracing: Fix very unlikely race of registering two stat tracers
tracing: Decrement trace_array when bootconfig creates an instance
tracing: Use pr_err() instead of WARN() for memory failures
----
include/trace/trace_events.h | 9 ++++++--- kernel/trace/ftrace.c | 4 ++-- kernel/trace/trace.c | 24 ++++++++++++++---------- kernel/trace/trace.h | 12 ++++++++++++ kernel/trace/trace_boot.c | 1 + kernel/trace/trace_entries.h | 2 +- kernel/trace/trace_stat.c | 31 +++++++++++++++++-------------- 7 files changed, 53 insertions(+), 30 deletions(-)
Steven Rostedt
maintainerPATCH 1/7 tracing: Fix very unlikely race of registering two stat tracers
From: "Steven Rostedt (VMware)" <[email protected]>
Looking through old emails in my INBOX, I came across a patch from Luis Henriques that attempted to fix a race of two stat tracers registering the same stat trace (extremely unlikely, as this is done in the kernel, and probably doesn't even exist). The submitted patch wasn't quite right as it needed to deal with clean up a bit better (if two stat tracers were the same, it would have the same files).
But to make the code cleaner, all we needed to do is to keep the all_stat_sessions_mutex held for most of the registering function.
--- kernel/trace/trace_stat.c | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-)
kernel/trace/trace_stat.c +9 -10
@@ -304,7 +304,7 @@ static int init_stat_file(struct stat_session *session)int register_stat_tracer (struct tracer_stat *trace) {struct stat_session *session, *node; -int ret; +int ret = -EINVAL ;if (!trace)return -EINVAL ;
@@ -315,17 +315,15 @@ int register_stat_tracer(struct tracer_stat *trace)/* Already registered? */ mutex_lock (&all_stat_sessions_mutex);list_for_each_entry (node, &all_stat_sessions, session_list) { -if (node->ts == trace) { -mutex_unlock (&all_stat_sessions_mutex); -return -EINVAL ; - } +if (node->ts == trace) + goto out; } -mutex_unlock (&all_stat_sessions_mutex); + ret = -ENOMEM ;/* Init the session */ session =kzalloc (sizeof (*session),GFP_KERNEL );if (!session) -return -ENOMEM ; + goto out; session->ts = trace;INIT_LIST_HEAD (&session->session_list);
@@ -334,15 +332,16 @@ int register_stat_tracer(struct tracer_stat *trace) ret =init_stat_file (session);if (ret) {destroy_session (session); -return ret; + goto out; } + ret =0 ;/* Register */ -mutex_lock (&all_stat_sessions_mutex);list_add_tail (&session->session_list, &all_stat_sessions); + out:mutex_unlock (&all_stat_sessions_mutex); -return 0 ; +return ret; }void unregister_stat_tracer (struct tracer_stat *trace)
Signature · 1 line
2.24.1
Steven Rostedt
maintainerPATCH 2/7 tracing: Fix tracing_stat return values in error handling paths
In reply to Steven RostedtFrom: Luis Henriques <[email protected]>
tracing_stat_init() was always returning '0', even on the error paths. It now returns -ENODEV if tracing_init_dentry() fails or -ENOMEM if it fails to created the 'trace_stat' debugfs directory.
--- kernel/trace/trace_stat.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
kernel/trace/trace_stat.c +8 -4
@@ -280,18 +280,22 @@ static int tracing_stat_init(void) d_tracing =tracing_init_dentry ();if (IS_ERR (d_tracing)) -return 0 ; +return -ENODEV ; stat_dir =tracefs_create_dir ("trace_stat" , d_tracing); -if (!stat_dir) +if (!stat_dir) {pr_warn ("Could not create tracefs 'trace_stat' entry\n" ); +return -ENOMEM ; + }return 0 ; }static int init_stat_file (struct stat_session *session) { -if (!stat_dir &&tracing_stat_init ()) -return -ENODEV ; +int ret; + +if (!stat_dir && (ret =tracing_stat_init ())) +return ret; session->file = tracefs_create_file(session->ts->name, 0644, stat_dir,
Signature · 1 line
2.24.1
Steven Rostedt
maintainerPATCH 3/7 tracing: Set kernel_stacks caller size properly
In reply to Steven RostedtFrom: Josef Bacik <[email protected]>
I noticed when trying to use the trace-cmd python interface that reading the raw buffer wasn't working for kernel_stack events. This is because it uses a stubbed version of __dynamic_array that doesn't do the __data_loc trick and encode the length of the array into the field. Instead it just shows up as a size of 0. So change this to __array and set the len to FTRACE_STACK_ENTRIES since this is what we actually do in practice and matches how user_stack_trace works.
--- kernel/trace/trace_entries.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/trace_entries.h +1 -1
@@ -174,7 +174,7 @@ FTRACE_ENTRY(kernel_stack, stack_entry,F_STRUCT (__field (int ,size ) - __dynamic_array(unsigned long, caller ) + __array( unsigned long, caller, FTRACE_STACK_ENTRIES ) ), F_printk("\t=> %ps\n\t=> %ps\n\t=> %ps\n"
Signature · 1 line
2.24.1
Steven Rostedt
maintainerPATCH 4/7 tracing: Remove unneeded NULL check
In reply to Steven RostedtFrom: Dan Carpenter <[email protected]>
We checked "iter->trace" earlier so there is no need to check here.
--- kernel/trace/trace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/trace.c +1 -1
@@ -4224,7 +4224,7 @@ __tracing_open(struct inode *inode, struct file *file, bool snapshot)mutex_init (&iter->mutex);/* Notify the tracer early; before we stop tracing. */ -if (iter->trace && iter->trace->open) +if (iter->trace->open) iter->trace->open (iter);/* Annotate start of buffers if we had overruns */
Signature · 1 line
2.24.1
Steven Rostedt
maintainerPATCH 5/7 tracing: Fix comments about trace/ftrace.h
In reply to Steven RostedtFrom: Hou Pengyang <[email protected]>
commit f42c85e74faa422cf0bc747ed808681145448f88 moved tracepoint's ftrace creation into include/trace/ftrace.h and trace/define_trace.h was deleted as a result. However some comment info does not adapt to the change, which is such a misguiding when reading related code.
This patch fix this by moving trace/trace_events.h to <trace/events/XXX.h>, since tracepoint headers have already been moved to tarce/events/.
--- include/trace/trace_events.h | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
include/trace/trace_events.h +6 -3
@@ -2,7 +2,8 @@/* * Stage 1 of the trace events. * -* Override the macros in <trace/trace_events.h> to include the following: +* Override the macros in the event tracepoint header <trace/events/XXX.h> +* to include the following: * * struct trace_event_raw_<call> { * struct trace_entry ent;
@@ -223,7 +224,8 @@ TRACE_MAKE_SYSTEM_STR();/* * Stage 3 of the trace events. * -* Override the macros in <trace/trace_events.h> to include the following: +* Override the macros in the event tracepoint header <trace/events/XXX.h> +* to include the following: * * enum print_line_t * trace_raw_output_<call>(struct trace_iterator *iter, int flags)
@@ -555,7 +557,8 @@ static inline notrace int trace_event_get_offsets_##call( \/* * Stage 4 of the trace events. * -* Override the macros in <trace/trace_events.h> to include the following: +* Override the macros in the event tracepoint header <trace/events/XXX.h> +* to include the following: * * For those macros defined with TRACE_EVENT: *
Signature · 1 line
2.24.1
Steven Rostedt
maintainerPATCH 6/7 tracing: Decrement trace_array when bootconfig creates an instance
In reply to Steven RostedtFrom: "Steven Rostedt (VMware)" <[email protected]>
The trace_array_get_by_name() creates a ftrace instance and trace_array_put() is used to remove the reference. Even though the trace_array_get_by_name() creates the instance, it also adds a reference count to it, that prevents user space from removing it.
As the bootconfig just creates the instance on boot up, it should still be used where it can be deleted by user space after boot. A trace_array_put() is required to let that happen.
Also, change the documentation on trace_array_get_by_name() to make this not be so confusing.
--- kernel/trace/trace.c | 4 ++++ kernel/trace/trace_boot.c | 1 + 2 files changed, 5 insertions(+)
kernel/trace/trace.c +4 -0
@@ -8602,6 +8602,10 @@ static int instance_mkdir(const char *name)* NOTE: This function increments the reference counter associated with the * trace array returned. This makes sure it cannot be freed while in use. * Use trace_array_put() once the trace array is no longer needed. +* If the trace_array is to be freed, trace_array_destroy() needs to +* be called after the trace_array_put(), or simply let user space delete +* it from the tracefs instances directory. But until the +* trace_array_put() is called, user space can not delete it. * */ struct trace_array *trace_array_get_by_name (const char *name)
kernel/trace/trace_boot.c +1 -0
@@ -327,6 +327,7 @@ trace_boot_init_instances(struct xbc_node *node)continue ; }trace_boot_init_one_instance (tr, inode); +trace_array_put (tr); } }
Signature · 1 line
2.24.1
Steven Rostedt
maintainerPATCH 7/7 tracing: Use pr_err() instead of WARN() for memory failures
In reply to Steven RostedtFrom: "Steven Rostedt (VMware)" <[email protected]>
As warnings can trigger panics, especially when "panic_on_warn" is set, memory failure warnings can cause panics and fail fuzz testers that are stressing memory.
Create a MEM_FAIL() macro to use instead of WARN() in the tracing code (perhaps this should be a kernel wide macro?), and use that for memory failure issues. This should stop failing fuzz tests due to warnings.
--- kernel/trace/ftrace.c | 4 ++-- kernel/trace/trace.c | 18 +++++++++--------- kernel/trace/trace.h | 12 ++++++++++++ 3 files changed, 23 insertions(+), 11 deletions(-)
kernel/trace/ftrace.c +2 -2
@@ -5459,7 +5459,7 @@ static void __init set_ftrace_early_graph(char *buf, int enable)struct ftrace_hash *hash; hash =alloc_ftrace_hash (FTRACE_HASH_DEFAULT_BITS ); -if (WARN_ON (!hash)) +if (MEM_FAIL (!hash,"Failed to allocate hash\n" ))return ;while (buf) {
@@ -6591,7 +6591,7 @@ static void add_to_clear_hash_list(struct list_head *clear_list, func =kmalloc (sizeof (*func),GFP_KERNEL );if (!func) { -WARN_ONCE (1 ,"alloc failure, ftrace filter could be stale\n" ); +MEM_FAIL (1 ,"alloc failure, ftrace filter could be stale\n" );return ; }
kernel/trace/trace.c +9 -9
@@ -3126,7 +3126,7 @@ static int alloc_percpu_trace_buffer(void)struct trace_buffer_struct *buffers; buffers = alloc_percpu(struct trace_buffer_struct); -if (WARN (!buffers,"Could not allocate percpu trace_printk buffer" )) +if (MEM_FAIL (!buffers,"Could not allocate percpu trace_printk buffer" ))return -ENOMEM ; trace_percpu_buffer = buffers;
@@ -7932,7 +7932,7 @@ static struct dentry *tracing_dentry_percpu(struct trace_array *tr, int cpu) tr->percpu_dir =tracefs_create_dir ("per_cpu" , d_tracer); -WARN_ONCE (!tr->percpu_dir, +MEM_FAIL (!tr->percpu_dir,"Could not create tracefs directory 'per_cpu/%d'\n" , cpu);return tr->percpu_dir;
@@ -8253,7 +8253,7 @@ create_trace_option_files(struct trace_array *tr, struct tracer *tracer)for (cnt =0 ; opts[cnt].name; cnt++) {create_trace_option_file (tr, &topts[cnt], flags, &opts[cnt]); -WARN_ONCE (topts[cnt].entry ==NULL , +MEM_FAIL (topts[cnt].entry ==NULL ,"Failed to create trace option: %s" , opts[cnt].name); }
@@ -8437,7 +8437,7 @@ static int allocate_trace_buffers(struct trace_array *tr, int size)#ifdef CONFIG_TRACER_MAX_TRACE ret =allocate_trace_buffer (tr, &tr->max_buffer, allocate_snapshot ? size :1 ); -if (WARN_ON (ret)) { +if (MEM_FAIL (ret,"Failed to allocate trace buffer\n" )) {ring_buffer_free (tr->array_buffer.buffer); tr->array_buffer.buffer =NULL ;free_percpu (tr->array_buffer.data);
@@ -8726,7 +8726,7 @@ static __init void create_trace_instances(struct dentry *d_tracer) trace_instance_dir =tracefs_create_instance_dir ("instances" , d_tracer, instance_mkdir, instance_rmdir); -if (WARN_ON (!trace_instance_dir)) +if (MEM_FAIL (!trace_instance_dir,"Failed to create instances directory\n" ))return ; }
@@ -8796,7 +8796,7 @@ init_tracer_tracefs(struct trace_array *tr, struct dentry *d_tracer)#endif if (ftrace_create_function_files (tr, d_tracer)) -WARN (1 ,"Could not allocate function filter files" ); +MEM_FAIL (1 ,"Could not allocate function filter files" );#ifdef CONFIG_TRACER_SNAPSHOT trace_create_file("snapshot", 0644, d_tracer,
@@ -9348,8 +9348,7 @@ __init static int tracer_alloc_buffers(void)/* TODO: make the number of buffers hot pluggable with CPUS */ if (allocate_trace_buffers (&global_trace, ring_buf_size) <0 ) { -printk (KERN_ERR "tracer: failed to allocate ring buffer!\n" ); -WARN_ON (1 ); +MEM_FAIL (1 ,"tracer: failed to allocate ring buffer!\n" ); goto out_free_savedcmd; }
@@ -9422,7 +9421,8 @@ void __init early_trace_init(void)if (tracepoint_printk) { tracepoint_print_iter =kmalloc (sizeof (*tracepoint_print_iter),GFP_KERNEL ); -if (WARN_ON (!tracepoint_print_iter)) +if (MEM_FAIL (!tracepoint_print_iter, +"Failed to allocate trace iterator\n" )) tracepoint_printk =0 ;else static_key_enable (&tracepoint_printk_key.key);
kernel/trace/trace.h +12 -0
@@ -94,6 +94,18 @@ enum trace_type {#include "trace_entries.h" +/* Use this for memory failure errors */ +#define MEM_FAIL (condition, fmt, ...) ({ \ + static bool __section(.data.once) __warned; \ + int __ret_warn_once = !!(condition); \ + \ + if (unlikely(__ret_warn_once && !__warned)) { \ + __warned = true; \ + pr_err("ERROR: " fmt, ##__VA_ARGS__); \ + } \ + unlikely(__ret_warn_once); \ +}) +/* * syscalls are special, and need special handling, this is why * they are not included in trace_entries.h
Signature · 1 line
2.24.1
Re: [for-next][PATCH 7/7] tracing: Use pr_err() instead of WARN() for memory failures
Quoted 9 lines · Steven Rostedt
From: "Steven Rostedt (VMware)" <[email protected]>
As warnings can trigger panics, especially when "
panic_on_warn" is set, memory failure warnings can cause panics and fail fuzz testers that are stressing memory.Create a
MEM_FAIL()macro to use instead ofWARN()in the tracing code (perhaps this should be a kernel wide macro?), and use that for memory failure issues. This should stop failing fuzz tests due to warnings.
It looks as if most of these could just be removed instead as there is an existing dump_stack() on failure.
kernel/trace/ftrace.c
Quoted 1 line
kernel/trace/ftrace.c +0
-0
[]
kernel/trace/ftrace.c static void __init set_ftrace_early_graph(char *buf, int enable) · line 5463
Quoted 7 lines
kernel/trace/ftrace.c +1
-1@@ -5459,7 +5459,7 @@ static void __init set_ftrace_early_graph(char *buf, int enable)struct ftrace_hash *hash; hash =alloc_ftrace_hash (FTRACE_HASH_DEFAULT_BITS ); -if (WARN_ON (!hash)) +if (MEM_FAIL (!hash,"Failed to allocate hash\n" ))return ;
has dump_stack()
kernel/trace/ftrace.c static void add_to_clear_hash_list(struct list_head *clear_list, · line 6594
Quoted 7 lines
kernel/trace/ftrace.c +1
-1while (buf) {@@ -6591,7 +6591,7 @@ static void add_to_clear_hash_list(struct list_head *clear_list, func =kmalloc (sizeof (*func),GFP_KERNEL );if (!func) { -WARN_ONCE (1 ,"alloc failure, ftrace filter could be stale\n" ); +MEM_FAIL (1 ,"alloc failure, ftrace filter could be stale\n" );
has dump_stack()
kernel/trace/trace.c
Quoted 1 line
kernel/trace/trace.c +0
-0
[]
kernel/trace/trace.c static int alloc_percpu_trace_buffer(void) · line 3130
Quoted 7 lines
kernel/trace/trace.c +1
-1@@ -3126,7 +3126,7 @@ static int alloc_percpu_trace_buffer(void)struct trace_buffer_struct *buffers; buffers = alloc_percpu(struct trace_buffer_struct); -if (WARN (!buffers,"Could not allocate percpu trace_printk buffer" )) +if (MEM_FAIL (!buffers,"Could not allocate percpu trace_printk buffer" ))return -ENOMEM ;
has dump_stack()
kernel/trace/trace.c static struct dentry *tracing_dentry_percpu(struct trace_array *tr, int cpu) · line 7936
Quoted 9 lines
kernel/trace/trace.c +1
-1trace_percpu_buffer = buffers;@@ -7932,7 +7932,7 @@ static struct dentry *tracing_dentry_percpu(struct trace_array *tr, int cpu) tr->percpu_dir =tracefs_create_dir ("per_cpu" , d_tracer); -WARN_ONCE (!tr->percpu_dir, +MEM_FAIL (!tr->percpu_dir,"Could not create tracefs directory 'per_cpu/%d'\n" , cpu);
keep?
Quoted 38 lines
kernel/trace/trace.c +4
-4return tr->percpu_dir;@@ -8253,7 +8253,7 @@ create_trace_option_files(struct trace_array *tr, struct tracer *tracer)for (cnt =0 ; opts[cnt].name; cnt++) {create_trace_option_file (tr, &topts[cnt], flags, &opts[cnt]); -WARN_ONCE (topts[cnt].entry ==NULL , +MEM_FAIL (topts[cnt].entry ==NULL ,"Failed to create trace option: %s" , opts[cnt].name); }@@ -8437,7 +8437,7 @@ static int allocate_trace_buffers(struct trace_array *tr, int size)#ifdef CONFIG_TRACER_MAX_TRACE ret =allocate_trace_buffer (tr, &tr->max_buffer, allocate_snapshot ? size :1 ); -if (WARN_ON (ret)) { +if (MEM_FAIL (ret,"Failed to allocate trace buffer\n" )) {ring_buffer_free (tr->array_buffer.buffer); tr->array_buffer.buffer =NULL ;free_percpu (tr->array_buffer.data);@@ -8726,7 +8726,7 @@ static __init void create_trace_instances(struct dentry *d_tracer) trace_instance_dir =tracefs_create_instance_dir ("instances" , d_tracer, instance_mkdir, instance_rmdir); -if (WARN_ON (!trace_instance_dir)) +if (MEM_FAIL (!trace_instance_dir,"Failed to create instances directory\n" ))return ; }@@ -8796,7 +8796,7 @@ init_tracer_tracefs(struct trace_array *tr, struct dentry *d_tracer)#endif if (ftrace_create_function_files (tr, d_tracer)) -WARN (1 ,"Could not allocate function filter files" ); +MEM_FAIL (1 ,"Could not allocate function filter files" );#ifdef CONFIG_TRACER_SNAPSHOT trace_create_file("snapshot", 0644, d_tracer,
kernel/trace/trace.c __init static int tracer_alloc_buffers(void) · line 9351
Quoted 6 lines
kernel/trace/trace.c +1
-2@@ -9348,8 +9348,7 @@ __init static int tracer_alloc_buffers(void)/* TODO: make the number of buffers hot pluggable with CPUS */ if (allocate_trace_buffers (&global_trace, ring_buf_size) <0 ) { -printk (KERN_ERR "tracer: failed to allocate ring buffer!\n" ); -WARN_ON (1 ); +MEM_FAIL (1 ,"tracer: failed to allocate ring buffer!\n" );
has dump_stack()
kernel/trace/trace.c void __init early_trace_init(void) · line 9425
Quoted 10 lines
kernel/trace/trace.c +2
-1goto out_free_savedcmd; }@@ -9422,7 +9421,8 @@ void __init early_trace_init(void)if (tracepoint_printk) { tracepoint_print_iter =kmalloc (sizeof (*tracepoint_print_iter),GFP_KERNEL ); -if (WARN_ON (!tracepoint_print_iter)) +if (MEM_FAIL (!tracepoint_print_iter, +"Failed to allocate trace iterator\n" ))
has dump_stack()
Quoted 26 lines
kernel/trace/trace.c +0
-0tracepoint_printk =0 ; else static_key_enable(&tracepoint_printk_key.key);kernel/trace/trace.h +12
-0@@ -94,6 +94,18 @@ enum trace_type {#include "trace_entries.h" +/* Use this for memory failure errors */ +#define MEM_FAIL (condition, fmt, ...) ({ \ + static bool __section(.data.once) __warned; \ + int __ret_warn_once = !!(condition); \ + \ + if (unlikely(__ret_warn_once && !__warned)) { \ + __warned = true; \ + pr_err("ERROR: " fmt, ##__VA_ARGS__); \ + } \ + unlikely(__ret_warn_once); \ +}) +/* * syscalls are special, and need special handling, this is why * they are not included in trace_entries.h
Steven Rostedt
maintainerRe: [for-next][PATCH 7/7] tracing: Use pr_err() instead of WARN() for memory failures
Quoted 7 lines · On Sun, 26 Jan 2020 12:38:55 -0800 Joe Perches <[email protected]> wrote:
Quoted 6 lines · Steven Rostedt
From: "Steven Rostedt (VMware)" <[email protected]>
As warnings can trigger panics, especially when "
panic_on_warn" is set, memory failure warnings can cause panics and fail fuzz testers that are stressing memory.
Quoted 6 lines
Quoted 3 lines
Create a
MEM_FAIL()macro to use instead ofWARN()in the tracing code (perhaps this should be a kernel wide macro?), and use that for memory failure issues. This should stop failing fuzz tests due to warnings.It looks as if most of these could just be removed instead as there is an existing
dump_stack()on failure.
That sounds more generic. This is specific for my own tracing tests to look for. As the point is, it is *not* to dump_stack, and still report the error.
-- Steve
Re: [for-next][PATCH 7/7] tracing: Use pr_err() instead of WARN() for memory failures
Quoted 14 lines · Steven Rostedt
Quoted 11 lines · On Sun, 26 Jan 2020 12:38:55 -0800 Joe Perches <[email protected]> wrote:
Quoted 9 lines · Steven Rostedt
From: "Steven Rostedt (VMware)" <[email protected]>
As warnings can trigger panics, especially when "
panic_on_warn" is set, memory failure warnings can cause panics and fail fuzz testers that are stressing memory.Create a
MEM_FAIL()macro to use instead ofWARN()in the tracing code (perhaps this should be a kernel wide macro?), and use that for memory failure issues. This should stop failing fuzz tests due to warnings.
Quoted 6 lines
Quoted 2 lines
It looks as if most of these could just be removed instead as there is an existing
dump_stack()on failure.That sounds more generic. This is specific for my own tracing tests to look for. As the point is, it is *not* to
dump_stack, and still report the error.
__GFP_NOWARN is available too.
Steven Rostedt
maintainerRe: [for-next][PATCH 7/7] tracing: Use pr_err() instead of WARN() for memory failures
Quoted 5 lines · On Sun, 26 Jan 2020 13:07:36 -0800 Joe Perches <[email protected]> wrote:
Quoted 3 lines
That sounds more generic. This is specific for my own tracing tests to look for. As the point is, it is *not* to
dump_stack, and still report the error.
__GFP_NOWARNis available too.
I honestly don't care if there's a dump_stack or not. I just removed the WARN_ON. If the allocation causes a dump_stack() then that's fine, but I still like to have a bit more information at what failed to allocate, than just a offset into a function.
The point of this patch was simply to remove WARN_ON() that caused fuzzers to fail.
-- Steve