mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Nick Piggin <piggin@cyberone.com.au>, Ingo Molnar <mingo@elte.hu>
Subject: scheduler BUGON lifespan
Date: Mon, 29 Nov 2004 13:11:34 -0800	[thread overview]
Message-ID: <1101762694.29380.23.camel@farah.beaverton.ibm.com> (raw)

I submitted a patch to active_load_balance() that was accepted into mm
and then mainline.  The patch included a fix to prevent the system
entering what should have been an impossible state.  The previous code
tested for it and then continued, rather than crashing or complaining.
My patch added a BUGON(impossible state) just in case by some fluke it
still happened.  How long should this BUGON remain in the kernel?  A
month, a year?  Is there an accepted duration for such safety nets?

Thanks,

-- 
Darren Hart <dvhltc@us.ibm.com>
IBM Linux Technology Center

             reply	other threads:[~2004-11-29 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 21:11 Darren Hart [this message]
2004-11-29 21:29 ` Andrew Morton
2004-11-29 22:32 ` Ingo Molnar

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=1101762694.29380.23.camel@farah.beaverton.ibm.com \
    --to=dvhltc@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=piggin@cyberone.com.au \
    /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
all inboxes | Powered by JetHome®