linux-kernel - Re: mount namespace : who mounted what ?

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: <4C08D1EF.4000104@free.fr>
Date:	Fri, 04 Jun 2010 12:14:07 +0200
From:	Daniel Lezcano <daniel.lezcano@...e.fr>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: mount namespace : who mounted what ?

On 06/04/2010 06:01 AM, Al Viro wrote:
> On Thu, Jun 03, 2010 at 10:04:13PM +0200, Daniel Lezcano wrote:
>    
>> Hi all,
>>
>> I was wondering, in a new mount namespace, if it is possible to know
>> which mount points were inherited and which were mounted in a new
>> namespace ?
>>
>> I looked at /proc/<pid>/mountinfo and investigated a bit on the
>> mount id, but this one is not reliable as it changes in the new
>> namespace. The /proc/<pid>/mounts file shows all the mount points
>> visible for the process inherited or not.
>>      
> No more than "had it been this process that mmaped that area or was it
> inherited from the parent?"
>    

Ok, thanks.

I thought it may be interessting to add this information in the procfs 
(eg. /proc/<pid>/mountprivate) but wrt your remark that should have no 
sense as, to be consistent, we should do the same for all kind of 
inherited resources.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/