+++ This bug was initially created as a clone of Bug #211857 +++ Problem description from 104660: The mount command doesn't support context options that contain commas. See this message for patches which should be applied to correct the problem: http: //article.gmane.org/gmane.linux.redhat.security.lspp/1004 -- Additional comment from eparis on 2006-11-21 21:11 EST -- I had no plan of putting a specific patch for FC6 as when davej next updates the FC6 kernel to 2.6.19 we will get it then. http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3528a95322b5c1ce882ab723f175a1845430cd89
This feature is temporarily disabled in util-linux-2.13-mount-context.patch.
I've encounter with similar behaviour but not exact the same. The forced context in this case is completely ignored ... [root@localhost vmware]# ls -Z /mnt/ drwxr-xr-x root root system_u:object_r:mnt_t:s0 foo [root@localhost vmware]# mount -t ntfs-3g -o loop,offset=32256,context=blabla ntfsImg-flat /mnt/foo/ [root@localhost vmware]# ls -Z /mnt/ drwxrwxrwx root root system_u:object_r:fusefs_t:s0 foo [root@localhost vmware]# umount /mnt/foo/ [root@localhost vmware]# mount -t ntfs-3g -o context=blabla:bleble:blabla,loop,offset=32256 ntfsImg-flat /mnt/foo/ [root@localhost vmware]# ls -Z /mnt/ drwxrwxrwx root root system_u:object_r:fusefs_t:s0 foo ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ But not in this case. [root@localhost vmware]# cat /dev/zero > file [root@localhost vmware]# mkfs.ext3 file ... [root@localhost vmware]# mount -o loop,context=system_u:object_r:httpd_sys_content_t:s0 file /mnt/foo/ [root@localhost vmware]# ls -Z /mnt/ drwxr-xr-x root root system_u:object_r:httpd_sys_content_t:s0 foo
It looks that the bug is dependent on the number of options.
mount(8) doesn't mount all filesystems. Try to use /sbin/mount.fuse (or .ntfs-3g) directly. IMHO this not a problem in mount(8).
Closing. FC6 is too old for new features.