From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: davem@davemloft.net, pankaj.laxminarayan.bharadiya@intel.com,
keescook@chromium.org, viro@zeniv.linux.org.uk, hare@suse.com,
tglx@linutronix.de, ktkhai@virtuozzo.com, edumazet@google.com,
arnd@arndb.de, axboe@kernel.dk, netdev@vger.kernel.org
Subject: [PATCH 0/2] unix: Show number of scm files in fdinfo
Date: Thu, 07 Nov 2019 15:14:15 +0300 [thread overview]
Message-ID: <157312863230.4594.18421480718399996953.stgit@localhost.localdomain> (raw)
Unix sockets like a block box. You never know what is pending there:
there may be a file descriptor holding a mount or a block device,
or there may be whole universes with namespaces, sockets with receive
queues full of sockets etc.
The patchset makes number of pending scm files be visible in fdinfo.
This may be useful to determine, that socket should be investigated
or which task should be killed to put reference counter on a resourse.
---
Kirill Tkhai (2):
net: Allow to show socket-specific information in /proc/[pid]/fdinfo/[fd]
unix: Show number of pending scm files of receive queue in fdinfo
include/linux/net.h | 1 +
include/net/af_unix.h | 5 ++++
net/socket.c | 12 +++++++++++
net/unix/af_unix.c | 56 +++++++++++++++++++++++++++++++++++++++++++++----
4 files changed, 69 insertions(+), 5 deletions(-)
--
Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
next reply other threads:[~2019-11-07 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 12:14 Kirill Tkhai [this message]
2019-11-07 12:14 ` [PATCH 1/2] net: Allow to show socket-specific information in /proc/[pid]/fdinfo/[fd] Kirill Tkhai
2019-11-07 12:14 ` [PATCH 2/2] unix: Show number of pending scm files of receive queue in fdinfo Kirill Tkhai
2019-11-08 19:30 ` [PATCH 0/2] unix: Show number of scm files " David Miller
2019-11-08 23:15 ` Jens Axboe
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=157312863230.4594.18421480718399996953.stgit@localhost.localdomain \
--to=ktkhai@virtuozzo.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hare@suse.com \
--cc=keescook@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=pankaj.laxminarayan.bharadiya@intel.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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).