public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <linux-kernel@borntraeger.net>
To: linux-kernel@vger.kernel.org
Cc: Tim Wright <timw@splhi.com>, Andrew Morton <akpm@osdl.org>, lmb@suse.de
Subject: Re: [PATCH] was: [RFC] removal of sync in panic
Date: Sun, 18 Jul 2004 09:34:12 +0200	[thread overview]
Message-ID: <200407180934.12418.linux-kernel@borntraeger.net> (raw)
In-Reply-To: <1090090902.14032.15.camel@kryten.internal.splhi.com>

Tim Wright wrote:
> Yes, I've seen this multiple times.
> I also agree that it seems a sensible patch. I have one dumb question.
> Given that we're panicing and we know things are "bad", is there any
> reason not to call smp_send_stop() as early as possible, rather than as
> the last thing which we currently do? As you say, the other cpus are
> happily continuing, potentially destroying data, and it seems that
> stopping this as quickly as possible would be desirable.

That suggestion was my number 2 is my first mail :-)

On the other hand, if we remove the sync stuff,  smp_send_stop is called 
quite early. Only a printf is called before smp_send_stop().  

  reply	other threads:[~2004-07-18  7:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 15:45 [RFC] removal of sync in panic Christian Borntraeger
2004-07-14 16:23 ` Lars Marowsky-Bree
2004-07-14 17:39   ` [PATCH] was: " Christian Borntraeger
2004-07-14 21:31     ` Andrew Morton
2004-07-15  4:58       ` Christian Borntraeger
2004-07-15  5:22         ` William Lee Irwin III
2004-07-17 19:01         ` Tim Wright
2004-07-18  7:34           ` Christian Borntraeger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-15  8:00 linux-kernel

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=200407180934.12418.linux-kernel@borntraeger.net \
    --to=linux-kernel@borntraeger.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    --cc=timw@splhi.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