From: Stephen Hemminger <stephen@networkplumber.org>
To: "j.ps@openmailbox.org" <j.ps@openmailbox.org>
Cc: netdev@vger.kernel.org
Subject: Re: Segmentation fault in iproute2 ss -p (versions 4.0.0, 4.1.0 and 4.1.1)
Date: Mon, 20 Jul 2015 12:09:54 -0700 [thread overview]
Message-ID: <20150720120954.2639f2e4@urahara> (raw)
In-Reply-To: <55AC9E25.9050804@openmailbox.org>
Patches are always appreciated and this looks like a real bug.
But before I can accept it there are a couple of small
changes needed.
1. There is no need to check for NULL when calling free().
Glibc free is documented to accept NULL as a valid request
and do nothing.
2. Please add a Signed-off-by: line with a real name.
Signed-off-by has legal meaning for the Developer's Certificate of Origin
see kernel documentation if you need more explaination.
3. Although what you found is important, giving a full paragraph
of personal comment about it is not required. The point is software
should read like one source independent of who the authors are.
Your comment is basically just justifying using strncpy.
4. Rather than strncpy() which has issues with maximal sized strings
consider using strlcpy() instead.
5. Iproute2 uses kernel identation and style, consider running checkpatch
on your changes.
Please fixup and resubmit to netdev.
next prev parent reply other threads:[~2015-07-20 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150719140548.6d17a475@urahara>
2015-07-20 7:07 ` Segmentation fault in iproute2 ss -p (versions 4.0.0, 4.1.0 and 4.1.1) j.ps
2015-07-20 19:09 ` Stephen Hemminger [this message]
2015-07-21 9:50 ` j.ps
2015-07-21 9:54 ` "ss -p" segfaults j.ps
2015-10-06 10:09 ` "ss -p" segfaults (updated to 4.2) Willy Tarreau
2015-10-10 14:34 ` j.ps
2015-10-12 16:50 ` Stephen Hemminger
2015-10-12 16:55 ` Willy Tarreau
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=20150720120954.2639f2e4@urahara \
--to=stephen@networkplumber.org \
--cc=j.ps@openmailbox.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;
as well as URLs for NNTP newsgroup(s).