From: Andrew Morton <akpm@osdl.org>
To: Christian Borntraeger <linux-kernel@borntraeger.net>
Cc: linux-kernel@vger.kernel.org, lmb@suse.de
Subject: Re: [PATCH] was: [RFC] removal of sync in panic
Date: Wed, 14 Jul 2004 14:31:12 -0700 [thread overview]
Message-ID: <20040714143112.1d8d1892.akpm@osdl.org> (raw)
In-Reply-To: <200407141939.52316.linux-kernel@borntraeger.net>
Christian Borntraeger <linux-kernel@borntraeger.net> wrote:
>
> Lars Marowsky-Bree wrote:
> > > 1. remove sys_sync completely: syslogd and klogd use fsync. No need to
> > > help them. Furthermore we have a severe problem which is worth a panic,
> > > so we better dont do any I/O.
>
> > I've seen exactly the behaviour you describe and would be inclined to go
> > for this option too.
>
> As this problem definitely exists, here is a patch.
>
> --- linux-2.6.8-rc1/kernel/panic.c 2004-06-16 07:20:04.000000000 +0200
> +++ linux-patch/kernel/panic.c 2004-07-14 19:37:02.000000000 +0200
> @@ -59,13 +59,7 @@ NORET_TYPE void panic(const char * fmt,
> va_start(args, fmt);
> vsnprintf(buf, sizeof(buf), fmt, args);
> va_end(args);
> - printk(KERN_EMERG "Kernel panic: %s\n",buf);
> - if (in_interrupt())
> - printk(KERN_EMERG "In interrupt handler - not syncing\n");
> - else if (!current->pid)
> - printk(KERN_EMERG "In idle task - not syncing\n");
> - else
> - sys_sync();
> + printk(KERN_EMERG "Kernel panic - not syncing: %s\n",buf);
> bust_spinlocks(0);
>
> #ifdef CONFIG_SMP
I agree with the patch in principle, but I'd be interested in what observed
problem motivated it?
next prev parent reply other threads:[~2004-07-14 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 15:45 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 [this message]
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
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=20040714143112.1d8d1892.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
/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®