Your message dated Mon, 15 Feb 2010 02:18:12 +0100 with message-id <[email protected]> and subject line Re: rlimit has caused the Debian Bug report #387668, regarding linux-image-2.6.17-2-powerpc: any user can lower process priority to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 387668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387668 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-image-2.6.17-2-powerpc Version: 2.6.17-9 Severity: normal Hi, since i've upgraded to this kernel, ANY user can setpriority his processes to lower priorities. #include <sys/time.h> #include <sys/resource.h> #include <stdio.h> #include <stdlib.h> #include <unistd.h> #include <sys/types.h> int main() { int priority; system("id"); priority = getpriority(PRIO_PROCESS, getpid()); printf("priority = %d\n", priority); if (setpriority(PRIO_PROCESS, getpid(), priority - 1) < 0) perror("setpriority"); priority = getpriority(PRIO_PROCESS, getpid()); printf("priority = %d\n", priority); return 0; } uid=1000(benoit) gid=1000(benoit) groupes=20(dialout),24(cdrom), \ 25(floppy),29(audio),44(video),46(plugdev),106(camera), \ 110(hal),116(fuse),118(scanner),1000(benoit) priority = 0 priority = -1 debsums is OK on my kernel. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages linux-image-2.6.17-2-powerpc depends on: ii mkvmlinuz 23 create a kernel to boot a PowerPC ii module-init-tools 3.2.2-3 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD linux-image-2.6.17-2-powerpc recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.17-2-powerpc/postinst/create-kimage-link-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/preinst/initrd-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/preinst/lilo-initrd-2.6.17-2-powerpc: true * linux-image-2.6.17-2-powerpc/preinst/already-running-this-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/preinst/abort-overwrite-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/prerm/removing-running-kernel-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/really-run-bootloader-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/preinst/elilo-initrd-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/depmod-error-2.6.17-2-powerpc: false linux-image-2.6.17-2-powerpc/postinst/kimage-is-a-directory: linux-image-2.6.17-2-powerpc/preinst/abort-install-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/postinst/old-dir-initrd-link-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/old-system-map-link-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/bootloader-test-error-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/preinst/overwriting-modules-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/bootloader-error-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/preinst/bootloader-initrd-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/old-initrd-link-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-powerpc/prerm/would-invalidate-boot-loader-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/preinst/failed-to-move-modules-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/postinst/depmod-error-initrd-2.6.17-2-powerpc: false
--- End Message ---
--- Begin Message ---On Tue, Sep 08, 2009 at 10:02:59PM +0200, Moritz Muehlenhoff wrote: > On Fri, Sep 15, 2006 at 11:11:10PM +0200, Benoît Dejean wrote: > > getrlimit nice gives me rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY > > on ppc. I have never touched these settings. I assume these are system > > default settings which have changed to unexpected and dangerous values > > (should be 0 i guess). > > Does this still occur with more recent kernels? No further feedback. If you can still reproduce this with a recent kernel, pleas reopen. Cheers, Moritz
--- End Message ---
