From: Pavel Emelyanov <xemul@parallels•com>
To: David Miller <davem@davemloft•net>
Cc: "netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"eric.dumazet@gmail•com" <eric.dumazet@gmail•com>
Subject: Re: [PATCH 2/2] unix: Add /proc/net/unix_peers file
Date: Mon, 05 Dec 2011 14:25:11 +0400 [thread overview]
Message-ID: <4EDC9C07.6070904@parallels.com> (raw)
In-Reply-To: <20111204.132510.1708510157080644595.davem@davemloft.net>
On 12/04/2011 10:25 PM, David Miller wrote:
> From: Pavel Emelyanov <xemul@parallels•com>
> Date: Thu, 01 Dec 2011 21:42:06 +0400
>
>> Currently it's not possible to find out what processes are connected
>> to each other via a unix socket. In the proposed proc file a socket
>> inode number and its peer inode number are shown. With these two at
>> hands it's possible to determine the unix connections endpoints.
>>
>> Signed-off-by: Pavel Emelyanov <xemul@parallels•com>
>
> I'm basically against new networking procfs based information
> retrieval mechanisms.
So am I, just wanted to bring this topic up again.
> Please extend the netlink socket dumping so that it works with
> AF_UNIX sockets and subsequently added the necessary netlink
> attribute to provide the peer value.
OK, will do it this way. AFAIU you're talking about the NETLINK_INET_DIAG, right?
> I plan to stand pretty firm on this, so you may want to save your
> effort and use said effort to implement this properly.
>
> Thanks.
> .
>
Thanks,
Pavel
next prev parent reply other threads:[~2011-12-05 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 17:41 [PATCH 0/2] unix: Introduce /proc/net/unix_peers file Pavel Emelyanov
2011-12-01 17:41 ` [PATCH 1/2] unix: Reformat proc files creation Pavel Emelyanov
2011-12-01 17:42 ` [PATCH 2/2] unix: Add /proc/net/unix_peers file Pavel Emelyanov
2011-12-04 18:25 ` David Miller
2011-12-05 10:25 ` Pavel Emelyanov [this message]
2011-12-05 23:47 ` David Miller
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=4EDC9C07.6070904@parallels.com \
--to=xemul@parallels$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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