All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Serge Hallyn <serge@hallyn.com>,
	James Morris <james.l.morris@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Aleksa Sarai <asarai@suse.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] exec: avoid gcc-8 warning for get_task_comm
Date: Tue, 5 Dec 2017 11:09:23 -0800	[thread overview]
Message-ID: <CAGXu5jLt4FtzavnngHGv=kagNrbCvM384CJK1to0atNb2hroJw@mail.gmail.com> (raw)
In-Reply-To: <20171205151724.1764896-1-arnd@arndb.de>

On Tue, Dec 5, 2017 at 7:17 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> gcc-8 warns about using strncpy() with the source size as the limit:
>
> fs/exec.c:1223:32: error: argument to 'sizeof' in 'strncpy' call is the same expression as the source; did you mean to use the size of the destination? [-Werror=sizeof-pointer-memaccess]
>
> This is indeed slightly suspicious, as it protects us from source
> arguments without NUL-termination, but does not guarantee that the
> destination is terminated.
>
> This keeps the strncpy() to ensure we have properly padded target buffer,
> but ensures that we use the correct length, by passing the actual length
> of the destination buffer as well as adding a build-time check to ensure
> it is exactly TASK_COMM_LEN.  There are only 23 callsights which I all
> reviewed to ensure this is currently the case. We could get away with
> doing only the check or passing the right length, but it doesn't hurt
> to do both.
>
> Suggested-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Awesome. Thanks for checking them all!

Acked-by: Kees Cook <keescook@chromium.org>

-Kees

> ---
>  fs/exec.c             | 7 +++----
>  include/linux/sched.h | 6 +++++-
>  2 files changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/fs/exec.c b/fs/exec.c
> index 6be2aa0ab26f..156f56acfe8e 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -1216,15 +1216,14 @@ static int de_thread(struct task_struct *tsk)
>         return -EAGAIN;
>  }
>
> -char *get_task_comm(char *buf, struct task_struct *tsk)
> +char *__get_task_comm(char *buf, size_t buf_size, struct task_struct *tsk)
>  {
> -       /* buf must be at least sizeof(tsk->comm) in size */
>         task_lock(tsk);
> -       strncpy(buf, tsk->comm, sizeof(tsk->comm));
> +       strncpy(buf, tsk->comm, buf_size);
>         task_unlock(tsk);
>         return buf;
>  }
> -EXPORT_SYMBOL_GPL(get_task_comm);
> +EXPORT_SYMBOL_GPL(__get_task_comm);
>
>  /*
>   * These functions flushes out all traces of the currently running executable
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 21991d668d35..5124ba709830 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -1503,7 +1503,11 @@ static inline void set_task_comm(struct task_struct *tsk, const char *from)
>         __set_task_comm(tsk, from, false);
>  }
>
> -extern char *get_task_comm(char *to, struct task_struct *tsk);
> +extern char *__get_task_comm(char *to, size_t len, struct task_struct *tsk);
> +#define get_task_comm(buf, tsk) ({                     \
> +       BUILD_BUG_ON(sizeof(buf) != TASK_COMM_LEN);     \
> +       __get_task_comm(buf, sizeof(buf), tsk);         \
> +})
>
>  #ifdef CONFIG_SMP
>  void scheduler_ipi(void);
> --
> 2.9.0
>



-- 
Kees Cook
Pixel Security

  reply	other threads:[~2017-12-05 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 15:17 [PATCH v2] exec: avoid gcc-8 warning for get_task_comm Arnd Bergmann
2017-12-05 19:09 ` Kees Cook [this message]
2017-12-06 10:11 ` David Laight
2017-12-06 17:49 ` Ingo Molnar
2017-12-06 23:09   ` Kees Cook
2017-12-06 23:29     ` Andrew Morton

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='CAGXu5jLt4FtzavnngHGv=kagNrbCvM384CJK1to0atNb2hroJw@mail.gmail.com' \
    --to=keescook@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=asarai@suse.de \
    --cc=ebiederm@xmission.com \
    --cc=frederic@kernel.org \
    --cc=james.l.morris@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=serge@hallyn.com \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.