public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David C. Hansen" <haveblue@us.ibm.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() at boot time
Date: Thu, 04 Apr 2002 08:23:49 -0800	[thread overview]
Message-ID: <3CAC7E15.203@us.ibm.com> (raw)
In-Reply-To: <20020404035910.A281@baldur.yggdrasil.com>

Adam J. Richter wrote:

>	When I attempted to boot linux-2.5.8-pre1, I got a kernel
>BUG() for exit.c line 519.
>
That bug is hit when the schedule() returns.  In the do_exit() case, 
schedule is not supposed to return.  After the current task is scheduled 
out, it is destroyed.  I guess that most of the freeing of the task's 
resources is done in do_exit(), but I don't see where its kernel stack 
is freed.  

> The was a small change to to kernel/exit.c
>in 2.5.8-pre1 which deleted a kernel_lock() call.  Restoring that line
>resulted in a kernel that booted fine.
>
I take it you don't have a copy of the BUG().   I was going to ask if 
preemption was enabled, but I see that it was from another message.  I 
was guessing that preemption contributed to this, but now I know.  The 
lock_kernel() has 2 different effects here.  It locks the kernel_flag, 
AND it disables preemption.  The correct fix here will probably be to 
disable preemption, rather than readd the lock_kernel().  

For the preemption gurus:
Is a preempt_disable() in do_exit() going to hurt anything?  Shold we 
selectively skip the preempt_disable() in schedule() if it was 
schedule() called from do_exit()?
--
Dave Hansen
haveblue@us.ibm.com


  parent reply	other threads:[~2002-04-04 16:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 11:59 Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() at boot time Adam J. Richter
2002-04-04 12:56 ` Stelian Pop
2002-04-04 13:40   ` Alessandro Suardi
2002-04-04 16:23 ` David C. Hansen [this message]
2002-04-04 18:28   ` Dave Hansen
2002-04-04 18:51     ` Robert Love
2002-04-04 19:14       ` Linus Torvalds
2002-04-04 19:26         ` Robert Love
2002-04-04 19:41           ` Dave Hansen
2002-04-04 20:02             ` Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() atboot time george anzinger
2002-04-04 20:54           ` Andrew Morton
2002-04-04 21:34           ` Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() at boot time Roger Larsson
2002-04-04 22:38             ` Andrew Morton
2002-04-04 22:42               ` Linus Torvalds
2002-04-04 22:54                 ` Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() atboot time Andrew Morton
2002-04-04 23:07                 ` Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() at boot time Robert Love
2002-04-04 23:42                   ` Linus Torvalds
2002-04-04 23:47                     ` Robert Love
2002-04-04 23:55                       ` Linus Torvalds
2002-04-05  0:03                         ` [PATCH] preemptive kernel behavior change: don't be rude Robert Love
2002-04-05  1:51                           ` george anzinger
2002-04-05  2:06                             ` Robert Love
2002-04-04 22:55               ` Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() at boot time Robert Love
2002-04-04 23:10                 ` Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() atboot time Andrew Morton
2002-04-04 23:16                   ` Robert Love
2002-04-04 19:13     ` Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() at boot time Linus Torvalds
2002-04-04 19:16       ` Robert Love
2002-04-04 19:45         ` Linus Torvalds
2002-04-04 20:09           ` Patch: linux-2.5.8-pre1/kernel/exit.c change caused BUG() atboot time george anzinger
2002-04-04 19:48       ` george anzinger

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=3CAC7E15.203@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox