Your message dated Sun, 08 Aug 2010 04:12:44 +0100 with message-id <1281237164.7543.131.camel@localhost> and subject line Re: linux-2.6: [x86] Null pointer dereference in hrtick_start_fair. has caused the Debian Bug report #538332, regarding linux-2.6: [x86] Null pointer dereference in hrtick_start_fair. 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 owner@bugs.debian.org immediately.) -- 538332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538332 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-2.6: [x86] Null pointer dereference in hrtick_start_fair.
- From: Alok Kataria <akataria@vmware.com>
- Date: Fri, 24 Jul 2009 14:33:38 -0700
- Message-id: <1248471218.9767.21.camel@ank32.eng.vmware.com>
- Reply-to: akataria@vmware.com
Package: linux-2.6 Version: Debian 5.0r2 Hi, There was a regression on mainline kernel due to my patches for tsc unification. It seems lenny has picked-up those unification patches but didn't pick the fix for that regression. I checked sources for Debian5 5.0r2 and its missing the fix. The commit details for the fix are commit 3d0decc4f49e8645cd6369b02ed076bebd3d61ad Author: Ingo Molnar <mingo@elte.hu> Date: Fri Jul 11 15:09:15 2008 +0200 x86: fix tsc unification buglet with ftrace and stackprotector Please include it in the next security update. We have seen null pointer de-reference in hrtick_start_fair during bootup, similar to one mentioned in the commit details. Thanks.
--- End Message ---
--- Begin Message ---
- To: 538332-done@bugs.debian.org
- Subject: Re: linux-2.6: [x86] Null pointer dereference in hrtick_start_fair.
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Sun, 08 Aug 2010 04:12:44 +0100
- Message-id: <1281237164.7543.131.camel@localhost>
My understanding of this bug report is that the bug does not affect upstream kernel versions 2.6.26 or 2.6.32 and therefore we do not need to make any change. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---