From: Russell King <rmk@arm.linux.org.uk>
To: Joshua Wise <jwise@google.com>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
ak@suse.de, benh@kernel.crashing.org, ink@jurassic.park.msu.ru,
linux-arch@vger.kernel.org, paulus@samba.org, rth@twiddle.net
Subject: Re: + print-utsname-on-oops-on-all-architectures.patch added to -mm tree
Date: Fri, 6 Jul 2007 22:54:44 +0100 [thread overview]
Message-ID: <20070706215444.GA1991@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0707061233450.617@internets.corp.google.com>
On Fri, Jul 06, 2007 at 02:03:45PM -0700, Joshua Wise wrote:
> On Fri, 6 Jul 2007, Russell King wrote:
> > On Fri, Jul 06, 2007 at 10:54:33AM -0700, akpm@linux-foundation.org wrote:
> > > Potential impact:
> > > This adds another line to the Oops output, causing the first few lines to
> > > potentially scroll off the screen. This also adds a few more pointer
> > > dereferences in the Oops path, because it adds to the die_chain notifier
> > > chain, reducing the likelihood that the Oops will be printed if there is
> > > very bad memory corruption.
> >
> > Plus we don't get the utsname information on oops dumps during the kernel
> > initialisation. Not good - I'd rather keep things as is rather than loose
> > that facility which we've just gained on ARM.
>
> Ok -- would it be more agreeable to make that a core_initcall?
That just makes the reporting slightly earlier and doesn't solve the
real problem.
> > Instead, can we have this as a call-able function which returns the
> > pointer, or just make the pointer global. That way we can also eliminate
> > the need for another additional line in the oops output.
>
> Hm. I don't really like the precedent being set for sucking arbitrary
> globals into the Oops message.
It's much safer than walking notifier lists and such like.
> In particular, I am also considering a patch to print machine check
> statistics (if we took any machine check exceptions) at Oops-time, and I
> would implement that in a similar manner to this.
I'm also going to raise an additional objection - whoever introduced
notify_die() hasn't bothered fixing up the ARM implementation, so your
patch actually _removes_ functionality recently introduced.
In addition, I notice that the introduction of notify_die() didn't take
account of what other architectures do (eg passing siginfo structures),
so to convert ARM to using it would either require us to drop some
functionality or re-engineer notify_die().
Therefore, I'm going to ask you to remove the changes from your patch
which touch the ARM architecture since the overall effect is a net
removal of functionality I've only recently merged.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-07-06 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 17:54 + print-utsname-on-oops-on-all-architectures.patch added to -mm tree akpm
2007-07-06 18:26 ` Russell King
2007-07-06 21:03 ` Joshua Wise
2007-07-06 21:54 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-13 8:23 akpm
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=20070706215444.GA1991@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jwise@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for NNTP newsgroup(s).