All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrei Vagin <avagin@openvz.org>
Cc: netdev@vger.kernel.org, Andrei Vagin <avagin@virtuozzo.com>
Subject: Re: [PATCH] ss: replace all zero characters in a unix name to '@'
Date: Tue, 4 Apr 2017 14:44:56 -0700	[thread overview]
Message-ID: <20170404144456.5e9b70fe@xeon-e3> (raw)
In-Reply-To: <1491010317-27083-1-git-send-email-avagin@openvz.org>

On Sat,  1 Apr 2017 04:31:57 +0300
Andrei Vagin <avagin@openvz.org> wrote:

> From: Andrei Vagin <avagin@virtuozzo.com>
> 
> A name of an abstract socket can contain zero characters.
> Now we replace only the first character. If a name contains more
> than one zero character, the ss tool shows only a part of the name:
> u_str  UNCONN    0    0     @                            1931097   * 0
> 
> the output with this patch:
> u_str  UNCONN    0    0     @@zdtm-./sk-unix-unconn-23/@ 1931097   * 0
> 
> Signed-off-by: Andrei Vagin <avagin@virtuozzo.com>

This patch duplicates changes that are already in current version.

commit 878dadc79d247aa37b67fb30608e58ef1f9ab9ff
Author: Isaac Boukris <iboukris@gmail.com>
Date:   Sat Oct 29 22:20:19 2016 +0300

    iproute2: ss: escape all null bytes in abstract unix domain socket
    
    Abstract unix domain socket may embed null characters,
    these should be translated to '@' when printed by ss the
    same way the null prefix is currently being translated.
    
    Signed-off-by: Isaac Boukris <iboukris@gmail.com>

      reply	other threads:[~2017-04-04 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01  1:31 [PATCH] ss: replace all zero characters in a unix name to '@' Andrei Vagin
2017-04-04 21:44 ` 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=20170404144456.5e9b70fe@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=avagin@openvz.org \
    --cc=avagin@virtuozzo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.