From: Johannes Bauer <JohannesBauer@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: x86_64 system lockup from userspace using setitimer()
Date: Tue, 13 Mar 2007 19:55:34 +0100 [thread overview]
Message-ID: <45F6F3A6.9060405@gmx.de> (raw)
Dear Community,
I think I've encountered a bug with the Linux kernel which results in a
complete system lockup and which can be started without root priviliges.
It's reproducible with 2.6.20.1 and 2.6.20.2 and only x64_64 seems affected.
Here's the code which triggers the bug (originally found by me using an
only partly initialized "struct itimerval" structure - hence the strange
values in it_interval):
-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----
#include <stdio.h>
#include <sys/time.h>
#include <unistd.h>
int main(int argc, char **argv) {
struct itimerval tim = {
.it_interval = {
.tv_sec = 140735669863712,
.tv_usec = 4199521
},
.it_value = {
.tv_sec = 0,
.tv_usec = 100000
}
};
setitimer(ITIMER_REAL, &tim, NULL);
while (1) sleep(1);
return 0;
}
-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----
Compiled with gcc 4.1.1 with "gcc -O2 -Wall -o crash crash.c".
The sourcecode can be found at
http://www.johannes-bauer.com/crash/crash.c and my kernel configuration
is at http://www.johannes-bauer.com/crash/config
Any further questions: feel free to ask. Please CC me for any posts in
this thread.
Greetings,
Johannes
--
"A PC without Windows is like a chocolate cake without mustard."
Johannes Bauer
91054 Erlangen
next reply other threads:[~2007-03-13 18:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 18:55 Johannes Bauer [this message]
2007-03-13 19:19 ` Andreas Schwab
2007-03-13 20:02 ` Chuck Ebbert
2007-03-13 20:33 ` Thomas Gleixner
2007-03-14 10:00 ` [PATCH] hrtimer: prevent overrun DoS in hrtimer_forward() Thomas Gleixner
2007-03-14 10:08 ` Ingo Molnar
2007-03-16 20:43 ` Andrew Morton
2007-03-16 21:05 ` Thomas Gleixner
2007-03-18 21:16 ` Chuck Ebbert
2007-03-18 21:32 ` Thomas Gleixner
2007-03-18 21:53 ` Chuck Ebbert
2007-03-18 22:04 ` Thomas Gleixner
2007-03-18 22:02 ` Chuck Ebbert
2007-04-04 21:11 ` Adrian Bunk
2007-04-04 21:30 ` Thomas Gleixner
2007-04-09 13:01 ` Adrian Bunk
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=45F6F3A6.9060405@gmx.de \
--to=johannesbauer@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome