Hi.

Before I am flamed again for creating a bug... This CVE is now open for
more than 6 months. It has been fixed in newer kernels, but for stable it
is still open. Is there any plan to fix it?

cu

AW
--
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (aw@linux.de)

On Mon, 2012-07-16 at 15:52 +0200, Arne Wichmann wrote:
> Hi.
>
> Before I am flamed again for creating a bug... This CVE is now open for
> more than 6 months. It has been fixed in newer kernels, but for stable it
> is still open. Is there any plan to fix it?

I believe the bug was introduced by:

commit a64692a3afd85fe048551ab89142fd5ca99a0dbd
Author: Mike Galbraith <efault@gmx.de>
Date: Thu Mar 11 17:16:20 2010 +0100

sched: Cleanup/optimize clock updates

(v2.6.35-rc1~521^2~41) and therefore does not affect stable. I'll
update kernel-sec accordingly.

Ben.

--
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.