>> You are forgetting that the fscred might simultaneously be
>> referenced by an open struct file. Are you saying that this
>> file should suddenly see its credential change?
> No, it cannot be referenced by an open struct file because you
> copy the structure, not pointers to it.
So you are proposing to optimize for the rare case of setuid(),
instead of the more common case of file open()?
Cheers,
Trond
-
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/