[lkml]   [2004]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: /proc/sys/kernel/pid_max issues

    > > this is a pretty sweeping assertion. Would you
    > > care to mention a few examples of such hazards?
    > kill(12345,9)
    > setpriority(PRIO_PROCESS,12345,-20)
    > sched_setscheduler(12345, SCHED_FIFO, &sp)
    > Prior to the call being handled, the process may
    > die and be replaced. Some random innocent process,
    > or a not-so-innocent one, will get acted upon by
    > mistake. This is broken and dangerous.
    > Well, it's in the UNIX standard. The best one can
    > do is to make the race window hard to hit, with LRU.

    Well, you could create new state "DEAD" and enforce that every process stays there for
    5 seconds after death. Throttle fork if no pids are free. Hide "DEAD" processes from ps/top.
    64 bytes from icmp_seq=28 ttl=51 time=448769.1 ms

    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 14:06    [W:0.023 / U:4.992 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site