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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 06 Aug 2010 10:05:06 +0200
From:	Daniel Lezcano <daniel.lezcano@...e.fr>
To:	Kay Sievers <kay.sievers@...y.org>
CC:	Chris Friesen <cfriesen@...tel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: mount notification question

On 08/06/2010 09:44 AM, Kay Sievers wrote:
> On Fri, Aug 6, 2010 at 03:07, Daniel Lezcano<daniel.lezcano@...e.fr>  wrote:
>    
>> On 08/04/2010 08:41 PM, Chris Friesen wrote:
>>      
>>> On 08/02/2010 03:12 PM, Daniel Lezcano wrote:
>>>        
>>>> is there a way to be notified when a mount occurs on the system ?
>>>>          
>>> Have you looked on google?  The link is a bit misleading but they do
>>> give a way to do it (not using inotify).
>>>
>>> http://stackoverflow.com/questions/1113176/how-could-i-detect-when-a-directory-is-mounted-with-inotify
>>>        
>> Thanks a lot for the pointer. I am not sure this solution will work, because
>> it is inadequate for watching a specific location in a container context
>> separated by the mount and the network namespaces. We have multiple mount
>> points at the same place (eg. the mount point inheritance, the container
>> configuration and the init scripts may mount /dev or /var/run several time)
>> and the network namespace separation will make impossible to watch udev
>> event via a netlink socket. I didn't look at the inotify implementation but
>> IMHO, it should be worth to add IN_MOUNT and IN_UNMOUNT events for inotify
>> no ?
>>      
> These events wouldn't work, and they are long removed from the kernel
> and don't exist.
>
> You need to poll() /proc/mounts, and any changes in it will wake you
> up with POLL_ERR. /proc/mounts should be namespace aware.
>    

Ah, great ! I will look for this solution (I suppose I will probably 
have to diff /proc/mounts but anyway ...)

Thanks Kay and Chris for your help.

   -- Daniel

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ