On Wed, Apr 29, 2015 at 01:10:34PM +0200, Beata Michalska wrote: > >>> It needs to be done internally by the app but is doable. > >>> The app knows what it is watching, so it can maintain the mappings. > >>> So prior to activating the notifications it can call 'stat' on the mount point. > >>> Stat struct gives the 'st_dev' which is the device id. Same will be reported > >>> within the message payload (through major:minor numbers). So having this, > >>> the app is able to get any other information it needs. > >>> Note that the events refer to the file system as a whole and they may not > >>> necessarily have anything to do with the actual block device. > > > > How are you going to show an event for a filesystem that is made up of > > multiple block devices? > > AFAIK, for such filesystems there will be similar case with the anonymous > major:minor numbers - at least the btrfs is doing so. Not sure we can > differentiate here the actual block device. So in this case such events > serves merely as a hint for the userspace. "hint" seems like this isn't really going to work well. Do you have userspace code that can properly map this back to the "real" device that is causing problems? Without that, this doesn't seem all that useful as no one would be able to use those events. > At this point a user might decide to run some scanning tools. You can't run a scanning tool on a tmpfs :) So what can a user do with information about one of these "virtual" filesystems that it can't directly see or access? > We might extend the scope of the > info being sent, though I would consider this as a nice-to-have but not > required for this initial version of notifications. The filesystems > might also want to decide to send their own custom messages so it is > possible for filesystems like btrfs to send more detailed information > using the new genetlink multicast group. > >> Or you can use /proc/self/mountinfo for the mapping. There you can see > >> device numbers, real device names if applicable and mountpoints. This has > >> the advantage that it works even if filesystem mountpoints change. > > > > Ok, then that brings up my next question, how does this handle > > namespaces? What namespace is the event being sent in? block devices > > aren't namespaced, but the mount points are, is that going to cause > > problems? > > > > The path should get resolved properly (as from root level). though I must > admit I'm not sure if there will be no issues when it comes to the network > namespaces. I'll double check it. Any hints though are more than welcomed :) What is "root level" here? You can mount things in different namespaces all over the place. This is going to get really complex very quickly :( I still think you should tie this to an existing sysfs device, which handles the namespace issues for you, and it also handles the fact that userspace can properly identify the device, if at all possible. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
