From: David Miller <davem@davemloft.net>
To: ktkhai@virtuozzo.com
Cc: 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, axboe@kernel.dk,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] unix: Show number of scm files in fdinfo
Date: Fri, 08 Nov 2019 11:30:03 -0800 (PST) [thread overview]
Message-ID: <20191108.113003.601469804110215285.davem@davemloft.net> (raw)
In-Reply-To: <157312863230.4594.18421480718399996953.stgit@localhost.localdomain>
From: Kirill Tkhai <ktkhai@virtuozzo.com>
Date: Thu, 07 Nov 2019 15:14:15 +0300
> 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.
This doesn't even compile:
net/unix/af_unix.c: In function ‘scm_stat_add’:
./include/linux/lockdep.h:365:52: error: invalid type argument of ‘->’ (have ‘spinlock_t’ {aka ‘struct spinlock’})
#define lockdep_is_held(lock) lock_is_held(&(lock)->dep_map)
^~
./include/asm-generic/bug.h:113:25: note: in definition of macro ‘WARN_ON’
int __ret_warn_on = !!(condition); \
^~~~~~~~~
./include/linux/lockdep.h:391:27: note: in expansion of macro ‘lockdep_is_held’
WARN_ON(debug_locks && !lockdep_is_held(l)); \
^~~~~~~~~~~~~~~
net/unix/af_unix.c:1582:2: note: in expansion of macro ‘lockdep_assert_held’
lockdep_assert_held(sk->sk_receive_queue.lock);
^~~~~~~~~~~~~~~~~~~
net/unix/af_unix.c: In function ‘scm_stat_del’:
./include/linux/lockdep.h:365:52: error: invalid type argument of ‘->’ (have ‘spinlock_t’ {aka ‘struct spinlock’})
#define lockdep_is_held(lock) lock_is_held(&(lock)->dep_map)
^~
./include/asm-generic/bug.h:113:25: note: in definition of macro ‘WARN_ON’
int __ret_warn_on = !!(condition); \
^~~~~~~~~
./include/linux/lockdep.h:391:27: note: in expansion of macro ‘lockdep_is_held’
WARN_ON(debug_locks && !lockdep_is_held(l)); \
^~~~~~~~~~~~~~~
net/unix/af_unix.c:1593:2: note: in expansion of macro ‘lockdep_assert_held’
lockdep_assert_held(sk->sk_receive_queue.lock);
^~~~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:266: net/unix/af_unix.o] Error 1
make[1]: *** [scripts/Makefile.build:509: net/unix] Error 2
make[1]: *** Waiting for unfinished jobs....
next prev parent reply other threads:[~2019-11-08 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 12:14 [PATCH 0/2] unix: Show number of scm files in fdinfo Kirill Tkhai
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 ` David Miller [this message]
2019-11-08 23:15 ` [PATCH 0/2] unix: Show number of scm files " 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=20191108.113003.601469804110215285.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=edumazet@google.com \
--cc=hare@suse.com \
--cc=keescook@chromium.org \
--cc=ktkhai@virtuozzo.com \
--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