linux-kernel - Re: task_diag: add a new interface to get information about processes

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] [day] [month] [year] [list]

Date:	Wed, 4 May 2016 15:34:21 -0700
From:	Andrey Vagin <avagin@...nvz.org>
To:	Stephen Hemminger <stephen@...workplumber.org>,
	Andy Lutomirski <luto@...capital.net>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	David Miller <davem@...emloft.net>
Subject: Re: task_diag: add a new interface to get information about processes

Hi Stephen,

On Wed, May 4, 2016 at 1:22 PM, Stephen Hemminger
<stephen@...workplumber.org> wrote:
> I understand how reading /proc or /sys can be a bottleneck, but this
> proposed method using a system call is the wrong way to do this.
>
> Why not use netlink like other systems do which allows a message
> based response which allows for future changes (no fixed datastructures),
> and is message based.
>
> Generic netlink has already been used by several other subsystems.

I used netlink in two first versions of task_diag, but then Andy
convinced me that netlink interfaces are not ideal for this case. I
added him into Cс.

Here is a thread with our discussion about using netlink for
task_diag: https://lkml.org/lkml/2015/12/15/520
Can I ask you to read it and give your comments? It would be nice to
find a way how to use netlink sockets instead of creating a new
interface.

Thanks,
Andrew