From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.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 10:23:43 -0400 [thread overview]
Message-ID: <20260713102343.74baba5b@gandalf.local.home> (raw)
In-Reply-To: <20260713121659.6c8549331474337511c4f442@kernel.org>
On Mon, 13 Jul 2026 12:16:59 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> > 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.
I don't see what else it could be.
>
> Jeongho, can you try this patch? Or/and you maybe also try using
> mlock the LMKD process memory which is passed to trace_marker.
Yes, Jeongho, can you please test this patch and also see if mlocking the
memory used by trace_marker would help too?
-- Steve
prev parent reply other threads:[~2026-07-13 14:29 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
2026-07-13 14:23 ` Steven Rostedt [this message]
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=20260713102343.74baba5b@gandalf.local.home \
--to=rostedt@goodmis.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=mhiramat@kernel.org \
--cc=minki.jang@samsung.com \
/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