From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH iproute2 v2 0/9] gcc-8 warning fixes
Date: Tue, 20 Mar 2018 11:19:34 -0700 [thread overview]
Message-ID: <20180320181943.4075-1-stephen@networkplumber.org> (raw)
This fixes most of the warnings when building with gcc-8.
Still have issues with namespace and bpf.
Stephen Hemminger (9):
bridge: avoid snprint truncation on time
pedit: fix strncpy warning
ip: use strlcpy() to avoid truncation
tunnel: use strlcpy to avoid strncpy warnings
namespace: fix warning snprintf buffer
tc_class: fix snprintf warning
ematch: fix possible snprintf overflow
misc: avoid snprintf warnings in ss and nstat
bpf: avoid compiler warnings about strncpy
bridge/mdb.c | 4 ++--
ip/iplink.c | 14 +++++++-------
ip/tunnel.c | 12 ++++++------
lib/bpf.c | 6 +++---
lib/namespace.c | 6 ++++--
misc/nstat.c | 4 ++--
misc/ss.c | 2 +-
tc/m_ematch.c | 2 +-
tc/m_pedit.c | 2 +-
tc/tc_class.c | 5 +++--
10 files changed, 30 insertions(+), 27 deletions(-)
--
2.16.2
next reply other threads:[~2018-03-20 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 18:19 Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-20 20:29 [PATCH iproute2 v2 0/9] gcc-8 warning fixes Stephen Hemminger
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=20180320181943.4075-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/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