[lkml]   [2002]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: problems with changing UID/GID

    On Tue, 27 Aug 2002, Chris Wedgwood wrote:
    > On Tue, Aug 27, 2002 at 09:42:27AM -0600, Thunder from the hill wrote:
    > I don't think this is cool. I mean, think of how many times we use
    > it, who will eat the overhead?
    > We use it almost never... a few times per process at most. And the
    > overhead will be nonexistent except in cases where the caller has to
    > wait on the lock --- and in those cases it seems totally reasonable they
    > *should* have to wait.

    And how do you protect a caller from having to wait for the lock? You'd
    need a lock count here, where you can only change the credentials when the
    count is zero. But when will that ever be?

    And btw, the count bumping/downing does cost. We need to do that sensibly.

    --./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .-
    --/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..-
    .- -/---/--/---/.-./.-./---/.--/.-.-.-

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:28    [W:0.030 / U:13.236 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site