netdev - Re: [PATCH iproute] iptuntap: show processes using tuntap interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160825084424.73a31b8a@xeon-e3>
Date:   Thu, 25 Aug 2016 08:44:24 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH iproute] iptuntap: show processes using tuntap interface

On Wed, 24 Aug 2016 20:08:25 +0200
Hannes Frederic Sowa <hannes@...essinduktion.org> wrote:

> Show which processes are using which tun/tap devices, e.g.:
> 
> $ ip -d tuntap
> tun0: tun
> 	Attached to processes: vpnc(9531)
> vnet0: tap vnet_hdr
> 	Attached to processes: qemu-system-x86(10442)
> virbr0-nic: tap UNKNOWN_FLAGS:800
> 	Attached to processes:
> 
> Signed-off-by: Hannes Frederic Sowa <hannes@...essinduktion.org>

I think reading all of /proc like this will scale really badly on large systems.
Why reinvent lsof?