[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1314405631.2970.283.camel@work-vm>
Date: Fri, 26 Aug 2011 17:40:31 -0700
From: john stultz <johnstul@...ibm.com>
To: lkml <linux-kernel@...r.kernel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>
Subject: [GIT PULL] Alarmtimer fixes for 3.1
Hey Thomas, Ingo, Andrew,
Again, these were sent out earlier but still haven't been pulled. I'm
leaving for vacation for the next two weeks (although I will
occasionally check email), so I wanted to resend this so it didn't get
missed.
In reviewing the alarmtimer code, I ran across a few bugs that should be
fixed for 3.1 and backported to 3.0-stable.
These are also available in the git repository at:
git://git.linaro.org/people/jstultz/linux.git fortglx/3.1/tip/timers/alarmtimers
The last of these is a pretty terrible hack, but I've got a more
invasive fix (along with other cleanups) queued on top of these for 3.2
that should resolve it. Feel free to take a peek at those changes here:
git://git.linaro.org/people/jstultz/linux.git fortglx/3.2/tip/timers/alarmtimers
Let me know if you have any thoughts or feedback!
thanks
-john
John Stultz (3):
alarmtimers: Avoid possible null pointer traversal
alarmtimers: Memset itimerspec passed into alarm_timer_get
alarmtimers: Avoid possible denial of service with high freq periodic
timers
kernel/time/alarmtimer.c | 18 +++++++++++++-----
1 files changed, 13 insertions(+), 5 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists