mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Kassey Li <quic_yingangl@quicinc.com>
Cc: <mingo@redhat.com>, <tj@kernel.org>,
	<william.kucharski@oracle.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] cgroup: align the comm length with TASK_COMM_LEN
Date: Sun, 25 Sep 2022 22:42:04 -0400	[thread overview]
Message-ID: <20220925224204.4e5d341e@gandalf.local.home> (raw)
In-Reply-To: <fee4b5ec-0e0d-8158-7e60-90f0918cab51@quicinc.com>

On Mon, 26 Sep 2022 10:18:55 +0800
Kassey Li <quic_yingangl@quicinc.com> wrote:

> >> @@ -139,12 +139,12 @@ DECLARE_EVENT_CLASS(cgroup_migrate,
> >>   		__entry->dst_level = dst_cgrp->level;
> >>   		__assign_str(dst_path, path);
> >>   		__entry->pid = task->pid;
> >> -		__assign_str(comm, task->comm);
> >> +		memcpy(__entry->comm, task->comm, TASK_COMM_LEN);  
> 	I think the problem is here, __assign_str using strcpy
> 	the task->comm here tail is not '\0'
> 	that's why it out of bounds access.
> 

If this is the case, then there's a lot more than just tracing that will
break. There are other places in the kernel has used strcpy() on task->comm,
and many more that do "%s" on task->comm, which would also crash on this.

> 	do you want to this version or just modify the memcpy or strncpy to do 
> with a known length ?  please give suggest so I can modify .

I'm guessing a problem exists elsewhere that makes it look like this is the
issue. I suggest finding where the '\0' is dropped (if that is indeed the
case).

-- Steve

  reply	other threads:[~2022-09-26  2:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  7:51 Kassey Li
2022-09-23 15:00 ` Steven Rostedt
2022-09-26  2:18   ` Kassey Li
2022-09-26  2:42     ` Steven Rostedt [this message]
2022-09-26 11:08       ` Kassey Li
2022-09-26 14:09 ` Steven Rostedt
2022-09-27  1:32   ` Kassey Li
2022-09-28  7:35   ` Kassey Li

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=20220925224204.4e5d341e@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=quic_yingangl@quicinc.com \
    --cc=tj@kernel.org \
    --cc=william.kucharski@oracle.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

all inboxes | Powered by JetHome®