openSUSE Kernel

Download

kernel@lists.opensuse.org

March 2014

22 participants
22 discussions

[opensuse-kernel] Is there a solution for the CVE-2014-0038 around?
by Stefan Hoese 07 Mar '14

07 Mar '14

Hello, did I miss something or is this [1][2] still unpatched in openSUSE 12.3 and 13.1 kernels? After: zypper in linux-sources and: grep -r -e "if (get_compat_timespec(&ktspec, timeout))" /usr/src/* there was the expected output for the _unpatched_ kernel. Much worse, the "CONFIG_X86_X32=y" (for openSUSE 13.1) and "CONFIG_X86_32=y" (for openSUSE 12.3) seems to be available in *every* kernel configuration. Is there a chance to use any kernel parameters for deactivating this problem? I didn't find any solution. Manually patching the kernel is no option for me. In the case of patching myself and the assumption that it will not be fixed in the repositories I will probably end up repairing this after every kernel update. Kind regards, Stefan References: [1] http://www.openwall.com/lists/oss-security/2014/01/31/2 [2] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=… -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

5 10

[opensuse-kernel] user/sys ticks for process exceed overall user/sys ticks
by Peter Hofer 06 Mar '14

06 Mar '14

Hello everyone! (I recently posted about this on linux-kernel, but got no responses. I would be very grateful for any pointers.) I am trying to determine what fraction of the whole system's user and sys time are consumed by a specific process, over a period of time. Hence, I read the respective tick counts from the first lines of /proc/stat and /proc/<pid>/stat at the start and end of that period and compute deltas. However, on an otherwise idle system, I often see the ticks consumed by a threaded process exceed those of the whole system. The difference is not just a few ticks, but can amount to over 10%, regardless of how long the observed time period is. There is no virtualization involved. I have been able to reproduce this with the current openSUSE and Ubuntu releases on different x86_64 machines. How can this be explained? Intuitively, I would expect that a tick accounted to a running task is at the same time accounted to the CPU it is running on, and so a process can never be accounted more ticks than the whole system, i.e. all CPUs. I have attached a simple Python script to reproduce this behavior. Example output: > ./ticks.py delta process: user: 2495 sys: 181 delta all: user: 2283 sys: 258 Thanks, Peter

3 9