Looks like I let this one slip through the cracks: Make RLIMIT_NICE ranges consistent with getpriority(2)
As suggested by Michael Kerrisk <[EMAIL PROTECTED]>, make RLIMIT_NICE consistent with getpriority before it becomes available in released glibc. Signed-off-by: Matt Mackall <[EMAIL PROTECTED]> Acked-by: Ingo Molnar <[EMAIL PROTECTED]> Acked-by: Chris Wright <[EMAIL PROTECTED]> Index: lhg/kernel/sched.c =================================================================== --- lhg.orig/kernel/sched.c 2005-08-15 13:03:05.000000000 -0700 +++ lhg/kernel/sched.c 2005-08-15 13:09:21.000000000 -0700 @@ -3378,8 +3378,8 @@ EXPORT_SYMBOL(set_user_nice); */ int can_nice(const task_t *p, const int nice) { - /* convert nice value [19,-20] to rlimit style value [0,39] */ - int nice_rlim = 19 - nice; + /* convert nice value [19,-20] to rlimit style value [1,40] */ + int nice_rlim = 20 - nice; return (nice_rlim <= p->signal->rlim[RLIMIT_NICE].rlim_cur || capable(CAP_SYS_NICE)); } -- Mathematics is the supreme nostalgia of our time. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/