From: john stultz <johnstul@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: [GIT PULL] Alarmtimer fixes for 3.1
Date: Fri, 26 Aug 2011 17:40:31 -0700 [thread overview]
Message-ID: <1314405631.2970.283.camel@work-vm> (raw)
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(-)
reply other threads:[~2011-08-27 0:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1314405631.2970.283.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox