From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, axboe@kernel.dk,
pankaj.laxminarayan.bharadiya@intel.com, keescook@chromium.org,
viro@zeniv.linux.org.uk, hare@suse.com, tglx@linutronix.de,
edumazet@google.com, arnd@arndb.de
Subject: Re: [PATCH net-next v2 0/2] unix: Show number of scm files in fdinfo
Date: Fri, 13 Dec 2019 10:37:59 +0300 [thread overview]
Message-ID: <57b6c0a4-285e-e429-2e87-41b5079974e1@virtuozzo.com> (raw)
In-Reply-To: <20191212.170506.1014670344797867509.davem@davemloft.net>
On 13.12.2019 04:05, David Miller wrote:
> From: Kirill Tkhai <ktkhai@virtuozzo.com>
> Date: Mon, 09 Dec 2019 13:03:34 +0300
>
>> v2: Pass correct argument to locked in patch [2/2].
>>
>> 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 a reference counter on a resourse.
>>
>> $cat /proc/[pid]/fdinfo/[unix_sk_fd] | grep scm_fds
>> scm_fds: 1
>
> Series applied.
Thanks, David.
prev parent reply other threads:[~2019-12-13 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 10:03 [PATCH net-next v2 0/2] unix: Show number of scm files in fdinfo Kirill Tkhai
2019-12-09 10:03 ` [PATCH net-next v2 1/2] net: Allow to show socket-specific information in /proc/[pid]/fdinfo/[fd] Kirill Tkhai
2019-12-09 10:03 ` [PATCH net-next v2 2/2] unix: Show number of pending scm files of receive queue in fdinfo Kirill Tkhai
2019-12-13 1:05 ` [PATCH net-next v2 0/2] unix: Show number of scm files " David Miller
2019-12-13 7:37 ` Kirill Tkhai [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=57b6c0a4-285e-e429-2e87-41b5079974e1@virtuozzo.com \
--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).