From: David Miller <davem@davemloft.net>
To: iboukris@gmail.com
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] unix: escape all null bytes in abstract unix domain socket
Date: Tue, 01 Nov 2016 12:15:33 -0400 (EDT) [thread overview]
Message-ID: <20161101.121533.1036644431036762336.davem@davemloft.net> (raw)
In-Reply-To: <1477960895-1062-1-git-send-email-iboukris@gmail.com>
From: Isaac Boukris <iboukris@gmail.com>
Date: Tue, 1 Nov 2016 02:41:35 +0200
> Abstract unix domain socket may embed null characters,
> these should be translated to '@' when printed out to
> proc the same way the null prefix is currently being
> translated.
>
> This helps for tools such as netstat, lsof and the proc
> based implementation in ss to show all the significant
> bytes of the name (instead of getting cut at the first
> null occurrence).
>
> Signed-off-by: Isaac Boukris <iboukris@gmail.com>
Applied, thank you.
prev parent reply other threads:[~2016-11-01 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 0:41 [PATCH v2] unix: escape all null bytes in abstract unix domain socket Isaac Boukris
2016-11-01 16:15 ` David Miller [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=20161101.121533.1036644431036762336.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=iboukris@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).