From: Nicholas Vinson <nvinson234@gmail•com>
To: mkubecek@suse•cz
Cc: Nicholas Vinson <nvinson234@gmail•com>, netdev@vger•kernel.org
Subject: [PATCH ethtool 0/3] Fix issues found by gcc -fanalyze
Date: Sun, 30 Apr 2023 18:50:49 -0400 [thread overview]
Message-ID: <cover.1682894692.git.nvinson234@gmail.com> (raw)
This patch series provides updates to correct issues found by gcc -fanalyze. The
issues were found by specifying the following flags when building:
CFLAGS="-march=native -O2 -pipe -fanalyzer -Werror=analyzer-va-arg-type-mismatch
-Werror=analyzer-va-list-exhausted -Werror=analyzer-va-list-leak
-Werror=analyzer-va-list-use-after-va-end"
CXXCFLAGS="-march=native -O2 -pipe -fanalyzer
-Werror=analyzer-va-arg-type-mismatch
-Werror=analyzer-va-list-exhausted
-Werror=analyzer-va-list-leak
-Werror=analyzer-va-list-use-after-va-end"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
GCC version is gcc (Gentoo 13.1.0-r1 p1) 13.1.0
Nicholas Vinson (3):
Update FAM syntax to conform to std C.
Fix reported memory leak.
Fix potentinal null-pointer derference issues.
ethtool.c | 24 +++++++++++++-----------
netlink/features.c | 24 ++++++++++++++++++------
2 files changed, 31 insertions(+), 17 deletions(-)
--
2.40.1
next reply other threads:[~2023-04-30 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 22:50 Nicholas Vinson [this message]
2023-04-30 22:50 ` [PATCH ethtool 1/3] Update FAM syntax to conform to std C Nicholas Vinson
2023-04-30 22:50 ` [PATCH ethtool 2/3] Fix reported memory leak Nicholas Vinson
2023-04-30 22:50 ` [PATCH ethtool 3/3] Fix potentinal null-pointer derference issues Nicholas Vinson
2023-05-07 22:57 ` Michal Kubecek
2023-05-08 2:46 ` Nicholas Vinson
2023-05-08 7:40 ` Michal Kubecek
2023-05-08 12:48 ` Nicholas Vinson
2023-05-07 22:40 ` [PATCH ethtool 0/3] Fix issues found by gcc -fanalyze patchwork-bot+netdevbpf
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=cover.1682894692.git.nvinson234@gmail.com \
--to=nvinson234@gmail$(echo .)com \
--cc=mkubecek@suse$(echo .)cz \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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