![]() | |||||||||||||
Messages in this thread |
>>- if (current->fsuid == inode->i_uid)>>+ if ((current->fsuid == inode->i_uid) && >>+ (current->nsproxy->user_ns == inode->i_sb->user_ns)) >> mode >>= 6; > > > I really don't think assigning a user namespace to a superblock is the > right way to go. Seems to me like the _view_ into the filesystem is > what you want to modify. That would seem to me to mean that each > 'struct namespace' (filesystem namespace) or vfsmount would be assigned > a corresponding user namespace, *not* the superblock. I dislike this way either. We need an ability to have an access to container filesystems and data from the host. such a strong checks break this. Thanks. Kirill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-07-16 08:39 [W:1.242 / U:0.260 seconds] ©2003-2008 Jasper Spaans | |||||||||||||