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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Wed, 20 Aug 2014 19:43:30 +0200
From:	Nicolas Dichtel <>
To:	Richard Guy Briggs <>,
	"Eric W. Biederman" <>
CC:,,,,, netdev <>
Subject: Re: [PATCH V3 0/6] namespaces: log namespaces per task

Le 20/08/2014 18:25, Richard Guy Briggs a écrit :
> On 14/08/19, Eric W. Biederman wrote:
>> Richard Guy Briggs <> writes:
>>> On 14/05/20, Richard Guy Briggs wrote:
>>>> On 14/05/20, Eric Paris wrote:
>>>>> On Tue, 2014-05-20 at 09:12 -0400, Richard Guy Briggs wrote:
>>>>>> The purpose is to track namespaces in use by logged processes from the
>>>>>> perspective of init_*_ns.
>>> (Including the Linux API list due to the additions to /proc/<pid>/ns/.
>>> Please see and in particular
>>> )
>> Sigh if you have to use something like this use the proc inode
>> number.  It is the same thing.
>> I hate to claim it is unique absent of the proc superblock but it is and
>> will be for the forseable future.
>> It would be better to include the block device number that appears in
>> proc of 3h of the primary mount of to qualify the number.  But it is not
>> particularly important.  Coming up with an additional unique number that
>> needs to be maintained seems stronlgy silly.
> I am reading a contradiction here:
> and this posting went completely ignored:
> And then there was this patchset and thread where there was some good
> discussion to clarify the use case:
> Then V2:
> Then V3 3 months ago:
> I'm about to post another version of the patchset addressing Eric Paris'
> concerns about record types, field naming...
I also try to find a solution to identify netns in userland to solve
some network problems (see

This serial number solution may be reused for this.
We really need to find a way to solve this.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists