From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: Masatake YAMATO <yamato@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/8] /proc/net/ entries for bluetooth protocols
Date: Tue, 10 Jul 2012 17:06:58 +0300 [thread overview]
Message-ID: <20120710140656.GB15795@aemeltch-MOBL1> (raw)
In-Reply-To: <20120618.190014.158443124058398316.yamato@redhat.com>
Hi Masatake,
On Mon, Jun 18, 2012 at 07:00:14PM +0900, Masatake YAMATO wrote:
> (I reflected the result of reviewing by Andrei.)
>
> lsof command can tell the type of socket processes are using.
> Internal lsof uses inode numbers on socket fs to resolve the type of
> sockets. Files under /proc/net/, such as tcp, udp, unix, etc provides
> such inode information.
>
> Unfortunately bluetooth related protocols don't provide such inode
> information. This patch series introduces /proc/net files for the protocols.
>
> This patch against af_bluetooth.c provides facility to the implementation
> of protocols. This patch extends bt_sock_list and introduces two exported
> function bt_procfs_init, bt_procfs_cleanup.
>
> The type bt_sock_list is already used in some of implementation of
> protocols. bt_procfs_init prepare seq_operations which converts
> protocol own bt_sock_list data to protocol own proc entry when the
> entry is accessed.
>
> What I, lsof user, need is just inode number of bluetooth
> socket. However, people may want more information. The bt_procfs_init
> takes a function pointer for customizing the show handler of
> seq_operations.
>
> Signed-off-by: Masatake YAMATO <yamato@redhat.com>
> ---
> include/net/bluetooth/bluetooth.h | 10 +++
> net/bluetooth/af_bluetooth.c | 136 +++++++++++++++++++++++++++++++++++++
> 2 files changed, 146 insertions(+)
>
> diff --git a/include/net/bluetooth/bluetooth.h b/include/net/bluetooth/bluetooth.h
> index 961669b..9c44977 100644
> --- a/include/net/bluetooth/bluetooth.h
> +++ b/include/net/bluetooth/bluetooth.h
> @@ -30,6 +30,7 @@
> #include <linux/list.h>
The line above was removed by commit
commit 8c520a59927a5600973782505dbb750d985057c4
Author: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Date: Wed May 23 04:04:22 2012 -0300
Bluetooth: Remove unnecessary headers include
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2012-07-10 14:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 17:15 [PATCH 1/8] /proc/net/ entries for bluetooth protocols Masatake YAMATO
2012-06-15 8:00 ` Andrei Emeltchenko
2012-06-17 0:26 ` Masatake YAMATO
2012-06-18 8:28 ` Andrei Emeltchenko
2012-06-28 17:02 ` Masatake YAMATO
2012-07-10 14:04 ` Andrei Emeltchenko
2012-07-11 4:58 ` [PATCH v3 1/8] bluetooth: " Masatake YAMATO
2012-07-11 4:59 ` [PATCH v3 2/8] bluetooth: Added /proc/net/bnep via bt_procfs_init() Masatake YAMATO
2012-07-25 0:20 ` Gustavo Padovan
2012-07-11 5:02 ` [PATCH v3 3/8] bluetooth: Added /proc/net/cmtp " Masatake YAMATO
2012-07-11 5:02 ` [PATCH v3 4/8] bluetooth: Added /proc/net/hci " Masatake YAMATO
2012-07-11 5:03 ` [PATCH v3 5/8] bluetooth: Added /proc/net/hidp " Masatake YAMATO
2012-07-11 5:03 ` [PATCH v3 6/8] bluetooth: Added /proc/net/l2cap " Masatake YAMATO
2012-07-11 8:48 ` Andrei Emeltchenko
2012-07-11 9:19 ` Masatake YAMATO
2012-07-11 9:49 ` Andrei Emeltchenko
2012-07-11 5:04 ` [PATCH v3 7/8] bluetooth: Added /proc/net/rfcomm " Masatake YAMATO
2012-07-11 8:49 ` Andrei Emeltchenko
2012-07-11 5:04 ` [PATCH v3 8/8] bluetooth: Added /proc/net/sco " Masatake YAMATO
2012-07-11 11:23 ` [PATCH v3 1/8] bluetooth: /proc/net/ entries for bluetooth protocols Andrei Emeltchenko
2012-07-11 12:19 ` Masatake YAMATO
2012-07-12 7:42 ` Andrei Emeltchenko
2012-07-16 13:20 ` [PATCH v4 " Masatake YAMATO
2012-07-25 0:12 ` Gustavo Padovan
2012-07-25 0:35 ` Gustavo Padovan
2012-07-25 16:26 ` [PATCH v5 1/8] Bluetooth: " Masatake YAMATO
2012-07-25 16:27 ` [PATCH v5 2/8] Bluetooth: Added /proc/net/bnep via bt_procfs_init() Masatake YAMATO
2012-07-25 16:28 ` [PATCH v5 3/8] Bluetooth: Added /proc/net/cmtp " Masatake YAMATO
2012-07-25 16:28 ` [PATCH v5 4/8] Bluetooth: Added /proc/net/hci " Masatake YAMATO
2012-07-25 16:29 ` [PATCH v5 5/8] Bluetooth: Added /proc/net/hidp " Masatake YAMATO
2012-07-25 16:29 ` [PATCH v5 6/8] Bluetooth: Added /proc/net/l2cap " Masatake YAMATO
2012-07-25 16:29 ` [PATCH v5 7/8] Bluetooth: Added /proc/net/rfcomm " Masatake YAMATO
2012-07-25 16:30 ` [PATCH v5 8/8] Added /proc/net/sco " Masatake YAMATO
2012-07-26 4:24 ` Gustavo Padovan
2012-08-15 15:22 ` Jan Engelhardt
2012-07-24 13:08 ` [PATCH v3 1/8] bluetooth: /proc/net/ entries for bluetooth protocols Masatake YAMATO
2012-07-24 13:15 ` Andrei Emeltchenko
2012-06-18 10:00 ` [PATCH v2 1/8] " Masatake YAMATO
2012-07-10 14:06 ` Andrei Emeltchenko [this message]
2012-06-18 10:00 ` [PATCH v2 2/8] Added /proc/net/bnep via bt_procfs_init() Masatake YAMATO
2012-06-18 10:01 ` [PATCH v2 3/8] Added /proc/net/cmtp " Masatake YAMATO
2012-06-18 10:01 ` [PATCH v2 4/8] Added /proc/net/hci " Masatake YAMATO
2012-06-18 10:03 ` [PATCH v2 5/8] Added /proc/net/hidp " Masatake YAMATO
2012-06-18 10:03 ` [PATCH v2 6/8] Added /proc/net/l2cap " Masatake YAMATO
2012-06-18 10:04 ` [PATCH v2 7/8] Added /proc/net/rfcomm " Masatake YAMATO
2012-06-18 10:04 ` [PATCH v2 8/8] Added /proc/net/sco " Masatake YAMATO
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=20120710140656.GB15795@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamato@redhat.com \
/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