All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: "Måns Rullgård" <mru@inprovide.com>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: can I bring Linux down by running "renice -20 cpu_intensive_process"?
Date: Fri, 17 Mar 2006 07:05:50 +0100	[thread overview]
Message-ID: <1142575550.8868.20.camel@homer> (raw)
In-Reply-To: <yw1xbqw69f6j.fsf@agrajag.inprovide.com>

On Thu, 2006-03-16 at 22:51 +0000, Måns Rullgård wrote:
> Bill Davidsen <davidsen@tmr.com> writes:
> 
> > Måns Rullgård wrote:
> >> Maybe extending sysrq+n to lower the priority of -20 tasks would be a
> >> good idea.
> >>
> > If it runs before the keyboard thread it doesn't matter...
> 
> Of course not, but that's not generally the case.
> 
> > But why should this hang anything, when there should be enough i/o
> > to get out of the user process. There's a good fix for this, don't
> > give this guy root any more ;-)
> 
> Ever heard of bugs?  Anyone developing a program can make a mistake.
> If the program runs with realtime scheduling a bug that makes it enter
> an infinite loop (or do something else that hogs the CPU) can be
> difficult to find since it rather efficiently locks you out.

Given that someone has already determined that installing a safety valve
for RT tasks was worth while, and given that there is practically no
difference between a nice -20 and the lowest RT priority, seems to me
that extending that safety valve to cover reniced tasks is the
obviously-correct thing to do.  I think you should submit a patch.

	-Mike


  reply	other threads:[~2006-03-17  6:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 13:36 can I bring Linux down by running "renice -20 cpu_intensive_process"? Tomasz Chmielewski
2006-03-10 14:44 ` Jan Engelhardt
2006-03-10 14:52   ` Tomasz Chmielewski
2006-03-10 22:01   ` Måns Rullgård
2006-03-10 22:06     ` Jeffrey Hundstad
2006-03-11 10:42       ` Måns Rullgård
2006-03-12  1:41     ` Luke-Jr
2006-03-12  3:46       ` Lee Revell
2006-03-12  3:50       ` Lee Revell
2006-03-12  3:44     ` Lee Revell
2006-03-12 12:00       ` Måns Rullgård
2006-03-16 21:15         ` Bill Davidsen
2006-03-16 22:11           ` Lee Revell
2006-03-16 22:51           ` Måns Rullgård
2006-03-17  6:05             ` Mike Galbraith [this message]
2006-03-17 22:22               ` Måns Rullgård
2006-03-18 12:38             ` Bill Davidsen

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=1142575550.8868.20.camel@homer \
    --to=efault@gmx.de \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@inprovide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.