From: Andrea Claudi <aclaudi@redhat.com>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, dsahern@gmail.com
Subject: [PATCH iproute2 0/2] lib: bpf_legacy: some misc fixes
Date: Mon, 19 Apr 2021 15:49:55 +0200 [thread overview]
Message-ID: <cover.1618839527.git.aclaudi@redhat.com> (raw)
This patch set fixes two issues on bpf_legacy library code.
- 1/2 fixes a covscan warning about a possible missing close() treating
0 as a valid file descriptor, as almost elsewhere in iproute2 code.
- 2/2 fixes a missing close() on a socket in some error paths in two
functions.
Andrea Claudi (2):
lib: bpf_legacy: treat 0 as a valid file descriptor
lib: bpf_legacy: fix missing socket close when connect() fails
lib/bpf_legacy.c | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)
--
2.30.2
next reply other threads:[~2021-04-19 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 13:49 Andrea Claudi [this message]
2021-04-19 13:49 ` [PATCH iproute2 1/2] lib: bpf_legacy: treat 0 as a valid file descriptor Andrea Claudi
2021-04-19 13:49 ` [PATCH iproute2 2/2] lib: bpf_legacy: fix missing socket close when connect() fails Andrea Claudi
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.1618839527.git.aclaudi@redhat.com \
--to=aclaudi@redhat.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).