linux-kernel - Re: [RFC v2 0/2] proc connector: get namespace events

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]

Message-ID: <87twcctk83.fsf@x220.int.ebiederm.org>
Date:   Sun, 16 Oct 2016 09:57:32 -0500
From:   ebiederm@...ssion.com (Eric W. Biederman)
To:     Alban Crequy <alban.crequy@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        containers@...ts.linux-foundation.org, netdev@...r.kernel.org,
        Iago Lopez Galeiras <iago@...volk.io>,
        Aaron Campbell <aaron@...key.org>,
        Jiri Benc <jbenc@...hat.com>,
        Jesper Derehag <jderehag@...mail.com>,
        Alban Crequy <alban@...volk.io>, Tejun Heo <tj@...nel.org>,
        Evgeniy Polyakov <zbr@...emap.net>,
        Dimitri John Ledkov <dimitri.j.ledkov@...el.com>
Subject: Re: [RFC v2 0/2] proc connector: get namespace events

Alban Crequy <alban.crequy@...il.com> writes:

> This is v2 of the patch set to add namespace events in the proc
> connector.

So while not totally wrong the way you report namespaces makes me
grumpy.  You are not including the device node of the filesystem
those inodes are on.  The inode number is meaningless if you don't
specify which filesystem the inode is from. 

I absolutely do not want to have to implement a namespace for namespaces
someday just because people have been sloppy like this.

So please correct this to at least report the full information on
namespaces.

Thank you,
Eric