From: Russell King <rmk@arm.linux.org.uk>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, jwise@google.com, 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 19:26:12 +0100 [thread overview]
Message-ID: <20070706182612.GA26179@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200707061754.l66HsXfb010994@imap1.linux-foundation.org>
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.
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.
--
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 18:27 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 [this message]
2007-07-06 21:03 ` Joshua Wise
2007-07-06 21:54 ` Russell King
-- 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=20070706182612.GA26179@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).