From: Steven Rostedt <rostedt@goodmis.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracepoint: don't make assumptions about length of string on task rename
Date: Fri, 28 Aug 2015 11:02:51 -0400 [thread overview]
Message-ID: <20150828110251.41b6b805@gandalf.local.home> (raw)
In-Reply-To: <1440760018-1557-1-git-send-email-sasha.levin@oracle.com>
On Fri, 28 Aug 2015 07:06:58 -0400
Sasha Levin <sasha.levin@oracle.com> wrote:
> While the dest comm string size is assured to be at least TASK_COMM_LEN long,
> doing a memcpy() also adds the assumption that the source is at least that
> long as well, which isn't assured, and isn't true in cases such as:
>
> set_task_comm(worker->task, "kworker/dying");
>
> This leads to accessing invalid memory.
>
> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
Should this go to stable as well?
Also, as the memcpy was just faster than a strcpy, the static length
was used. Perhaps we should convert that to a dynamic length string.
But that should be a separate patch as this one fixes a possible bug,
and the conversion to a dynamic string is just an enhancement.
-- Steve
> ---
> include/trace/events/task.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/trace/events/task.h b/include/trace/events/task.h
> index dee3bb1..2cca6cd 100644
> --- a/include/trace/events/task.h
> +++ b/include/trace/events/task.h
> @@ -46,7 +46,7 @@ TRACE_EVENT(task_rename,
> TP_fast_assign(
> __entry->pid = task->pid;
> memcpy(entry->oldcomm, task->comm, TASK_COMM_LEN);
> - memcpy(entry->newcomm, comm, TASK_COMM_LEN);
> + strlcpy(entry->newcomm, comm, TASK_COMM_LEN);
> __entry->oom_score_adj = task->signal->oom_score_adj;
> ),
>
next prev parent reply other threads:[~2015-08-28 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 11:06 Sasha Levin
2015-08-28 15:02 ` Steven Rostedt [this message]
2015-09-01 15:07 ` Sasha Levin
2015-09-01 15:32 ` 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=20150828110251.41b6b805@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sasha.levin@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®