From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netdev@vger.kernel.org
Subject: Re: [iproute PATCH v2 0/2] Covscan: Fix potential file descriptor leaks
Date: Fri, 18 Aug 2017 09:18:30 -0700 [thread overview]
Message-ID: <20170818091830.395db3e0@xeon-e3> (raw)
In-Reply-To: <20170817170931.24224-1-phil@nwl.cc>
On Thu, 17 Aug 2017 19:09:29 +0200
Phil Sutter <phil@nwl.cc> wrote:
> This series collects patches from v1 which deal with potential file
> descriptor leaks.
>
> No changes to the actual patches, just splitting into smaller series.
>
> Phil Sutter (2):
> ss: Don't leak fd in tcp_show_netlink_file()
> tc/em_ipset: Don't leak sockfd on error path
>
> misc/ss.c | 32 ++++++++++++++++++++------------
> tc/em_ipset.c | 1 +
> 2 files changed, 21 insertions(+), 12 deletions(-)
>
Applied
prev parent reply other threads:[~2017-08-18 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 17:09 [iproute PATCH v2 0/2] Covscan: Fix potential file descriptor leaks Phil Sutter
2017-08-17 17:09 ` [iproute PATCH v2 1/2] ss: Don't leak fd in tcp_show_netlink_file() Phil Sutter
2017-08-17 17:09 ` [iproute PATCH v2 2/2] tc/em_ipset: Don't leak sockfd on error path Phil Sutter
2017-08-18 16:18 ` Stephen Hemminger [this message]
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=20170818091830.395db3e0@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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