From: Lars Marowsky-Bree <lmb@suse.de>
To: Christian Borntraeger <linux-kernel@borntraeger.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] removal of sync in panic
Date: Wed, 14 Jul 2004 18:23:57 +0200 [thread overview]
Message-ID: <20040714162357.GU3922@marowsky-bree.de> (raw)
In-Reply-To: <200407141745.47107.linux-kernel@borntraeger.net>
On 2004-07-14T17:45:46,
Christian Borntraeger <linux-kernel@borntraeger.net> said:
> I can imagine several changes but I am not sure if this is a problem which
> must be fixed and which fix is the best.
> Here are my alternatives:
>
> 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.
> 3. Add an
> if (doing_io())
> printk(KERN_EMERG "In I/O routine - not syncing\n");
> check like in_interrupt check. Unfortunately I have no clue how this can be
> achieved and it looks quite ugly.
This would also work of course, but as you point out, it's more complex.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \ ever tried. ever failed. no matter.
SUSE Labs, Research and Development | try again. fail again. fail better.
SUSE LINUX AG - A Novell company \ -- Samuel Beckett
next prev parent reply other threads:[~2004-07-14 16:24 UTC|newest]
Thread overview: 8+ 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 [this message]
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
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=20040714162357.GU3922@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-kernel@borntraeger.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.