From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: netdev@vger.kernel.org
Cc: Craig Small <csmall@debian.org>, Vic Abell <vabell@lsof.comcastbiz.net>
Subject: Re: newline characters in unix socket names and /proc/net/unix
Date: Tue, 17 Mar 2015 21:27:27 +0000 [thread overview]
Message-ID: <20150317212727.GB9874@chaz.gmail.com> (raw)
In-Reply-To: <20150314223342.GA4146@chaz.gmail.com>
2015-03-14 22:33:42 +0000, Stephane Chazelas:
[...]
> it seems the kernel doesn't escape newline characters in the
> file names displayed in /proc/net/unix
[...]
> and is used by things like fuser, lsof for instance to map Inode
> to Path (and libgtop, systemd (to check which sockets are still
> in use for cleanup) at least).
[...]
A solution for fuser and lsof (at least) would be to use the new
netlink-based API where available (like "ss -ax" does on recent
systems) that doesn't have the problem.
For lsof, that would also mean (for linux-3.3 and above) that it
could display information about the peer of the socket (like it
does with lsof -E for pipes).
--
Stephane
prev parent reply other threads:[~2015-03-17 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 22:33 newline characters in unix socket names and /proc/net/unix Stephane Chazelas
2015-03-17 21:27 ` Stephane Chazelas [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=20150317212727.GB9874@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=csmall@debian.org \
--cc=netdev@vger.kernel.org \
--cc=vabell@lsof.comcastbiz.net \
/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).