> Right, I figure if the normal action is to always do
> mnt->user = current->fsuid, then for the special case we
> pass a uid in someplace. Of course... do we not have a
> place to do that? Would it be a no-no to use 'data' for
> a non-fs-specific arg?
I guess it would be OK for bind, but not for new- and remounts, where
'data' is already used.
Maybe it's best to stay with fsuid after all, and live with having to
restore capabilities. It's not so bad after all, this seems to do the
trick:
cap_t cap = cap_get_proc();
setfsuid(uid);
cap_set_proc(cap);
Unfortunately these functions are not in libc, but in a separate
"libcap" library. Ugh.
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
