All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	herton@mandriva.com.br, dvgevers@xs4all.nl
Subject: Re: [local DoS] Re: Linux 2.6.24-rc4
Date: Tue, 4 Dec 2007 14:04:25 -0200	[thread overview]
Message-ID: <20071204140425.05b0b458@mandriva.com.br> (raw)
In-Reply-To: <20071204160005.GA29783@elte.hu>

Em Tue, 4 Dec 2007 17:00:05 +0100
Ingo Molnar <mingo@elte.hu> escreveu:

| 
| * Linus Torvalds <torvalds@linux-foundation.org> wrote:
| 
| > 
| > 
| > On Tue, 4 Dec 2007, Luiz Fernando N. Capitulino wrote:
| > >
| > > 	sched_rr_get_interval(1, NULL);
| > 
| > Looks like we have a zero "cfs_rq->load.weight".
| > 
| > Ingo? Both sched_slice() and __sched_slice() do a divide by the 
| > runqueue weight, and at least dequeue_task_fair() explicitly checks 
| > for that being zero, so clearly zero is a possible value. Hmm?
| 
| yeah, i can reproduce this crash too.
| 
| The problem is on SMP: if sched_rr_get_interval() gets a task from an 
| otherwise idle runqueue, then rq->load.weight is 0. Normally 
| sched_slice() is only used on a busy runqueue. So the correct fixup site 
| is not in sched_slice() but in sys_sched_rr_get_interval() - i'm working 
| on the right fix, i hope to be able to send a pull request in a few 
| minutes.

 Ingo, I can reproduce this w/o SMP support as well.

 (Also, the backtrace I sent was reproduced on a UP machine with a
SMP kernel).

-- 
Luiz Fernando N. Capitulino

  reply	other threads:[~2007-12-04 16:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04  5:08 Linux 2.6.24-rc4 Linus Torvalds
2007-12-04 10:23 ` [build failure] Re: Linux 2.6.24-rc4 on S390x Kamalesh Babulal
2007-12-04 10:31   ` Martin Schwidefsky
2007-12-04 10:32   ` Ingo Molnar
2007-12-04 13:22 ` Linux 2.6.24-rc4 Nicolas Pitre
2007-12-04 16:04   ` Jeff Garzik
2007-12-04 14:07 ` [local DoS] " Luiz Fernando N. Capitulino
2007-12-04 15:56   ` Linus Torvalds
2007-12-04 16:00     ` Ingo Molnar
2007-12-04 16:04       ` Luiz Fernando N. Capitulino [this message]
2007-12-04 16:08         ` Ingo Molnar
2007-12-04 16:18       ` [git pull] scheduler fixes Ingo Molnar
2007-12-04 16:40         ` Luiz Fernando N. Capitulino
2007-12-04 18:28         ` Greg KH
2007-12-04 18:41           ` Luiz Fernando N. Capitulino
2007-12-04 21:04             ` Ingo Molnar
2007-12-04 20:51 ` Linux 2.6.24-rc4 Maciej Rutecki
2007-12-04 21:06   ` Linus Torvalds
2007-12-04 21:19     ` Maciej Rutecki
2007-12-04 21:23   ` ATA ACPI (was Re: Linux 2.6.24-rc4) Jeff Garzik
2007-12-04 21:25     ` Jeff Garzik
2007-12-04 21:25       ` Alan Cox
2007-12-04 21:27     ` Jeff Garzik
2007-12-04 22:48       ` Maciej Rutecki
2007-12-04 23:00         ` Jeff Garzik
2007-12-05  7:46           ` Maciej Rutecki
2007-12-10  8:42             ` Tejun Heo
2007-12-05  0:23 ` Linux 2.6.24-rc4 Diego Calleja

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=20071204140425.05b0b458@mandriva.com.br \
    --to=lcapitulino@mandriva.com.br \
    --cc=dvgevers@xs4all.nl \
    --cc=herton@mandriva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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 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.