From: Andi Kleen <ak@suse.de>
To: netdev@vger.kernel.org
Subject: Re: hard hang through qdisc II
Date: Thu, 31 Jan 2008 13:43:13 +0100 [thread overview]
Message-ID: <200801311343.13669.ak@suse.de> (raw)
In-Reply-To: <200801311321.01015.ak@suse.de>
On Thursday 31 January 2008 13:21:00 Andi Kleen wrote:
>
> I just managed to hang a 2.6.24 (+ some non network patches) kernel
> with the following (non sensical) command
Correction: the kernel was actually a git linus kernel with David's
recent merge included.
I found it's pretty easy to hang the kernel with various tbf parameters.
-Andi
> tc qdisc add dev eth0 root tbf rate 1000 burst 10 limit 100
>
> No oops or anything just hangs. While I understand root can
> do bad things just hanging like this seems a little extreme.
>
> -Andi
>
prev parent reply other threads:[~2008-01-31 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 12:21 hard hang through qdisc Andi Kleen
2008-01-31 12:34 ` jamal
2008-01-31 13:28 ` Andi Kleen
2008-01-31 13:29 ` Patrick McHardy
2008-01-31 14:02 ` Patrick McHardy
2008-01-31 15:04 ` Andi Kleen
2008-01-31 15:12 ` Patrick McHardy
2008-01-31 18:46 ` Patrick McHardy
2008-01-31 18:55 ` Andi Kleen
2008-01-31 12:43 ` Andi Kleen [this message]
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=200801311343.13669.ak@suse.de \
--to=ak@suse.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).