From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>
Subject: Re: Divide-by-zero in the 2.6.23 scheduler code
Date: Wed, 14 Nov 2007 14:56:05 +0100 [thread overview]
Message-ID: <20071114135605.GC3739@elte.hu> (raw)
In-Reply-To: <1195046856.6924.21.camel@twins>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> As for the patch, better to just rip out the entire feature..
for -stable it's safer to have smaller patches - so this patch is
perfectly fine. A user can turn it back on under SCHED_DEBUG and by
tweaking a debug flag - but that's not a big issue, you can mess up the
system in numerous ways via /proc/sys anyway. So i'd suggest Chuck's
patch for -stable.
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
next prev parent reply other threads:[~2007-11-14 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 1:14 Divide-by-zero in the 2.6.23 scheduler code Chuck Ebbert
2007-11-14 13:27 ` Peter Zijlstra
2007-11-14 13:56 ` Ingo Molnar [this message]
2007-11-14 14:06 ` Dmitry Adamushko
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=20071114135605.GC3739@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=cebbert@redhat.com \
--cc=dmitry.adamushko@gmail.com \
--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