From: Chris Mason <mason@suse.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: David <david@blue-labs.org>, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] report
Date: Fri, 16 Mar 2001 01:27:45 -0500 [thread overview]
Message-ID: <681360000.984724065@tiny> (raw)
In-Reply-To: <Pine.GSO.4.21.0103160056060.10709-100000@weyl.math.psu.edu>
On Friday, March 16, 2001 01:03:20 AM -0500 Alexander Viro
<viro@math.psu.edu> wrote:
>> Ok, I was more talking about the ugliness that is reiserfs_panic (how
>> many times do we need a commented out for(;;)?). For panic() calling
>> sys_sync, I think there non-filesystem related panics where we do want
>> to sync.
>
> panic doesn't sync if called from interrupt (thanks $DEITY).
> It is pointless to sync during boot.
> sync from driver panic is not better than one from fs.
>
> What does it leave? I hadn't checked each panic(), but it seems that
> if we ever want syncing upon panic() it's safer to do sys_sync() by
> hands before calling panic(). If it is actually ever needed, that is.
>
>
A quick grep -r shows over 700 panic callers (outside reiserfs). Most look
like init messages, or things that generally happen during interrupts.
But, I think there are too many to assume that nobody could benefit from a
sync.
Does that mean they _need_ the sync? Probably not.
-chris
prev parent reply other threads:[~2001-03-16 6:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 2:07 [OOPS] report David
2001-03-16 2:44 ` Alexander Viro
2001-03-16 5:29 ` Chris Mason
2001-03-16 5:32 ` Alexander Viro
2001-03-16 5:51 ` Chris Mason
2001-03-16 6:03 ` Alexander Viro
2001-03-16 6:27 ` Chris Mason [this message]
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=681360000.984724065@tiny \
--to=mason@suse.com \
--cc=david@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.