SH> 'capable' actually has an adverse effect of setting the SH> PF_SUPERPRIV flag on current. So if I don't misread this, you'll SH> want to do the length check first, then the capable check, in SH> order to make sure that PF_SUPERPRIV doesn't get set unless the SH> privilege was actually needed. Ah, okay, thanks, I'll switch those. -- Dan Smith IBM Linux Technology Center email: danms@xxxxxxxxxx _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
