From: David Laight <David.Laight@ACULAB.COM>
To: 'Arnd Bergmann' <arnd@arndb.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Kees Cook <keescook@chromium.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>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] exec: avoid gcc-8 warning for get_task_comm
Date: Wed, 6 Dec 2017 10:11:27 +0000 [thread overview]
Message-ID: <cc2e084d0a2f413b93e8929cbb413a40@AcuMS.aculab.com> (raw)
In-Reply-To: <20171205151724.1764896-1-arnd@arndb.de>
From: Arnd Bergmann
> Sent: 05 December 2017 15:17
> gcc-8 warns about using strncpy() with the source size as the limit:
Hmmm... Someone 'fixed' some of those in the NetBSD tree a few years back.
There was one place where the code was correct.
A potentially unterminated string was being copied into a buffer that was
one byte longer.
David
next prev parent reply other threads:[~2017-12-06 10:11 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
2017-12-06 10:11 ` David Laight [this message]
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=cc2e084d0a2f413b93e8929cbb413a40@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--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=keescook@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).