Skip to contentSkip to conversation

utimes() with vfat is problematic

DISCUSSION Bodo Eggert 1 participant 1 message Jul 11, 2007 1 message not in the archive VFS

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 17 lines · Jan Engelhardt

vfat does not know about ownership, hence the files are always owned by the vfat mounter (or whatever the uid= option specified). Which brings a problem to userspace programs trying to utime() but which do not run as the same user as the vfat mounter, because:

fs/attr.c:53
ret = -EPERM;
[...]

/* Check for setting the inode time. */
if (ia_valid & (ATTR_MTIME_SET | ATTR_ATIME_SET)) { if (current->fsuid != inode->i_uid && !capable(CAP_FOWNER))

                        goto error;
        }
Quoted 6 lines

To trigger the problem:

# mount /somevfat -o umask=0,uid=root
$ touch -d "2005-05-05" /somevfat/myfile

I am not sure how this could be dealt with besides passing -o quiet to mount.vfat. Any ideas?

Would it be possible to allow any user to modify the fs by adding "&& current->fsuid != -1"? I think it's commonly the desired behaviour. Off cause the default behaviour should stay the same.

Signature · 8 lines
Those who hesitate under fire usually do not end up KIA or WIA. 

Friß, Spammer: [email protected] [email protected]
 [email protected] [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html