From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netdev@vger.kernel.org
Subject: Re: [iproute PATCH v4 0/4] Covscan: Fix potential NULL pointer dereferences
Date: Thu, 24 Aug 2017 14:51:33 -0700 [thread overview]
Message-ID: <20170824145133.2b5d9730@xeon-e3> (raw)
In-Reply-To: <20170824094634.4093-1-phil@nwl.cc>
On Thu, 24 Aug 2017 11:46:30 +0200
Phil Sutter <phil@nwl.cc> wrote:
> This series collects patches from v1 which eliminate possible cases of
> NULL pointer dereferences.
>
> Changes since v3:
> - Dropped upstream rejected patch 2.
>
> Phil Sutter (4):
> ifstat, nstat: Check fdopen() return value
> tc/q_netem: Don't dereference possibly NULL pointer
> tc/tc_filter: Make sure filter name is not empty
> tipc/bearer: Prevent NULL pointer dereference
>
> misc/ifstat.c | 16 +++++++++++-----
> misc/nstat.c | 16 +++++++++++-----
> tc/q_netem.c | 3 ++-
> tc/tc_filter.c | 3 +++
> tipc/bearer.c | 2 +-
> 5 files changed, 28 insertions(+), 12 deletions(-)
>
Applied. Thanks
prev parent reply other threads:[~2017-08-24 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 9:46 [iproute PATCH v4 0/4] Covscan: Fix potential NULL pointer dereferences Phil Sutter
2017-08-24 9:46 ` [iproute PATCH v4 1/4] ifstat, nstat: Check fdopen() return value Phil Sutter
2017-08-24 9:46 ` [iproute PATCH v4 2/4] tc/q_netem: Don't dereference possibly NULL pointer Phil Sutter
2017-08-24 9:46 ` [iproute PATCH v4 3/4] tc/tc_filter: Make sure filter name is not empty Phil Sutter
2017-08-24 9:46 ` [iproute PATCH v4 4/4] tipc/bearer: Prevent NULL pointer dereference Phil Sutter
2017-08-24 21:51 ` 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=20170824145133.2b5d9730@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;
as well as URLs for NNTP newsgroup(s).