lkml.org 
[lkml]   [2001]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH] new setprocuid syscall
    From

    [BERECZ Szabolcs]
    > The conclusion: it's cannot be implemented without slowdown.

    Or: it cannot be implemented 100% safely and correctly without slowdown.

    If you know the use you wish to put this to, and are willing to risk a
    permission check somewhere being confused momentarily by a non-atomic
    update of a 32-bit number (or the non-atomic update between several
    32-bit numbers, which I think is less serious because then you are not
    granting more than the union of the two UIDs) go ahead and patch your
    kernel.

    > So ignore my patch.

    For official kernels, I agree. They need to be as safe and
    deterministic as possible, especially security-wise, and a semaphore on
    every permission check would be ridiculous.

    Peter
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:17    [W:0.022 / U:2.024 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site