lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 6 Dec 2017 18:49:34 +0100
From:   Ingo Molnar <>
To:     Arnd Bergmann <>
Cc:     Alexander Viro <>,
        Ingo Molnar <>,
        Peter Zijlstra <>,
        Kees Cook <>,
        Serge Hallyn <>,
        James Morris <>,
        Andrew Morton <>,
        Aleksa Sarai <>,
        "Eric W. Biederman" <>,
        Frederic Weisbecker <>,
        Thomas Gleixner <>,,
Subject: Re: [PATCH v2] exec: avoid gcc-8 warning for get_task_comm

* Arnd Bergmann <> 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 <>
> Signed-off-by: Arnd Bergmann <>

Looks useful.

Acked-by: Ingo Molnar <>



Powered by blists - more mailing lists