Linux Trace Kernel
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jeongho Choi <jh1012.choi@samsung.com>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	ji2yoon.jo@samsung.com, minki.jang@samsung.com,
	hajun.sung@samsung.com
Subject: Re: [BUG] tracing: Too many tries to read user space
Date: Mon, 13 Jul 2026 12:16:59 +0900	[thread overview]
Message-ID: <20260713121659.6c8549331474337511c4f442@kernel.org> (raw)
In-Reply-To: <20260710083357.49e05ff6@gandalf.local.home>

On Fri, 10 Jul 2026 08:33:57 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Fri, 10 Jul 2026 12:22:31 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> 
> > Hm, in my view, this warning indicates that the circuit breaker has
> > triggered correctly, so that is not a bug. Under the heavy memory
> > pressure and low-memory situation, the page can be reclaimed soon
> > after it is copied.
> 
> So you are saying that every time the copy_from_user() is executed, the
> page is reclaimed? And this causes a schedule?
> 
> Now, I did have a version that used sched_switch and only incremented the
> counter when a non-kernel thread was scheduled in. Then the test would
> check if the counter increased by 2 or more. As an increase by 1 meant that
> only kernel threads scheduled in which would not corrupt the buffer. The 1
> increment was the current task scheduling back.
> 
> This is based on that work (I'm glad I save old versions in my git tree :-)
> 
> Funny, the comments were from the original change I did back in August of
> 2025, which mentions kernel threads scheduling in to handle the fault.
> 
> I also kept this around in case it was needed. Looks like it may be needed.

Hmm, it's not clear whether this is the result of a scheduling storm
caused by kernel threads. But maybe worth to try.

Jeongho, can you try this patch? Or/and you maybe also try using
mlock the LMKD process memory which is passed to trace_marker.

Thank you, 

> 
> -- Steve
> 
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 18710c190c92..19354fe2fca1 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -53,6 +53,8 @@
>  #include <linux/io.h> /* vmap_page_range() */
>  #include <linux/fs_context.h>
>  
> +#include <trace/events/sched.h>
> +
>  #include <asm/setup.h> /* COMMAND_LINE_SIZE */
>  
>  #include "trace.h"
> @@ -5984,6 +5986,32 @@ struct trace_user_buf {
>  static DEFINE_MUTEX(trace_user_buffer_mutex);
>  static struct trace_user_buf_info *trace_user_buffer;
>  
> +static DEFINE_PER_CPU(unsigned long, sched_switch_cnt);
> +
> +/*
> + * The per CPU buffer trace_user_buffer is written to optimstically.
> + * The counter sched_switch_cnt is taken, preemption is enabled,
> + * the copying of the user space memory is placed into the trace_user_buffer,
> + * Preeption is re-enabled and the count is read again. If the count is greater
> + * than one from its previous reading, it means that another user space
> + * task scheduled in and the buffer is unreliable for use.
> + */
> +static void
> +probe_sched_switch(void *ignore, bool preempt,
> +		   struct task_struct *prev, struct task_struct *next,
> +		   unsigned int prev_state)
> +{
> +	/*
> +	 * The buffer can only be corrupted by another user space task.
> +	 * Ignore kernel tasks that may be scheduled in order to process
> +	 * the faulting memory.
> +	 */
> +	if (!is_user_task(next))
> +		return;
> +
> +	this_cpu_inc(sched_switch_cnt);
> +}
> +
>  /**
>   * trace_user_fault_destroy - free up allocated memory of a trace user buffer
>   * @tinfo: The descriptor to free up
> @@ -6003,6 +6031,8 @@ void trace_user_fault_destroy(struct trace_user_buf_info *tinfo)
>  		kfree(buf);
>  	}
>  	free_percpu(tinfo->tbuf);
> +
> +	unregister_trace_sched_switch(probe_sched_switch, NULL);
>  }
>  
>  static int user_fault_buffer_enable(struct trace_user_buf_info *tinfo, size_t size)
> @@ -6053,11 +6083,17 @@ static int user_buffer_init(struct trace_user_buf_info **tinfo, size_t size)
>  
>  	lockdep_assert_held(&trace_user_buffer_mutex);
>  
> +	ret = register_trace_sched_switch(probe_sched_switch, NULL);
> +	if (ret < 0)
> +		return ret;
> +
>  	if (!*tinfo) {
>  		alloc = true;
>  		*tinfo = kzalloc_obj(**tinfo);
> -		if (!*tinfo)
> +		if (!*tinfo) {
> +			unregister_trace_sched_switch(probe_sched_switch, NULL);
>  			return -ENOMEM;
> +		}
>  	}
>  
>  	ret = user_fault_buffer_enable(*tinfo, size);
> @@ -6241,7 +6277,7 @@ char *trace_user_fault_read(struct trace_user_buf_info *tinfo,
>  			return NULL;
>  
>  		/* Read the current CPU context switch counter */
> -		cnt = nr_context_switches_cpu(cpu);
> +		cnt = this_cpu_read(sched_switch_cnt);
>  
>  		/*
>  		 * Preemption is going to be enabled, but this task must
> @@ -6272,12 +6308,19 @@ char *trace_user_fault_read(struct trace_user_buf_info *tinfo,
>  			return NULL;
>  
>  		/*
> -		 * Preemption is disabled again, now check the per CPU context
> -		 * switch counter. If it doesn't match, then another user space
> -		 * process may have schedule in and corrupted our buffer. In that
> -		 * case the copying must be retried.
> +		 * Preemption is disabled again, now check the sched_switch_cnt.
> +		 * If it increased by two or more, then another user space process
> +		 * may have schedule in and corrupted our buffer. In that case
> +		 * the copying must be retried.
> +		 *
> +		 * Note, if this task was scheduled out and only kernel threads
> +		 * were scheduled in (maybe to process the fault), then the
> +		 * counter would increment again when this task scheduled in.
> +		 * If this task scheduled out and another user task scheduled
> +		 * in, this task would still need to be scheduled back in and
> +		 * the counter would increment by at least two.
>  		 */
> -	} while (nr_context_switches_cpu(cpu) != cnt);
> +	} while (this_cpu_read(sched_switch_cnt) > cnt + 1);
>  
>  	return buffer;
>  }


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-07-13  3:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20260708123754epcas2p1f15cc305ddb09f97164491d750769ef7@epcas2p1.samsung.com>
2026-07-08 12:37 ` [BUG] tracing: Too many tries to read user space Jeongho Choi
2026-07-08 13:18   ` Steven Rostedt
2026-07-09  0:04     ` Masami Hiramatsu
2026-07-10  3:22   ` Masami Hiramatsu
2026-07-10 11:46     ` Steven Rostedt
2026-07-13  2:55       ` Masami Hiramatsu
2026-07-10 12:33     ` Steven Rostedt
2026-07-13  3:16       ` Masami Hiramatsu [this message]
2026-07-13 14:23         ` Steven Rostedt

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=20260713121659.6c8549331474337511c4f442@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=hajun.sung@samsung.com \
    --cc=jh1012.choi@samsung.com \
    --cc=ji2yoon.jo@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=minki.jang@samsung.com \
    --cc=rostedt@goodmis.org \
    /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