From: Andrew Morton <akpm@osdl.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@muc.de>,
Hugh Dickens <hugh@veritas.com>,
Michael Ellerman <michael@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH RFC 1/4] Generic BUG handling.
Date: Thu, 28 Sep 2006 16:32:56 -0700 [thread overview]
Message-ID: <20060928163256.aa53b8d7.akpm@osdl.org> (raw)
In-Reply-To: <20060928225452.229936605@goop.org>
On Thu, 28 Sep 2006 15:54:45 -0700
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> This patch adds common handling for kernel BUGs, for use by
> architectures as they wish. The code is derived from arch/powerpc.
>
> The advantages of having common BUG handling are:
> - consistent BUG reporting across architectures
> - shared implementation of out-of-line file/line data
>
> This means that in inline impact of BUG is just the illegal
> instruction itself, which is an improvement for i386 and x86-64.
>
> A BUG is represented in the instruction stream as an illegal
> instruction, which has file/line/function information associated with
> it. This extra information is stored in the __bug_table section in
> the ELF file.
>
> When the kernel gets an illegal instruction, it first confirms it
> might possibly be from a BUG (ie, in kernel mode, the right illegal
> instruction). It then calls report_bug(). This searches __bug_table
> for a matching instruction pointer, and if found, prints the
> corresponding file/line/function information.
>
> Some architectures (powerpc) implement WARN using the same mechanism;
> if the illegal instruction was the result of a WARN, then report_bug()
> returns 1; otherwise it returns 0.
Neato.
> lib/bug.c keeps a list of loaded modules which can be searched for
> __bug_table entries. The architecture must call
> module_bug_finalize()/module_bug_cleanup() from its corresponding
> module_finalize/cleanup functions.
What is the locking for these lists? I don't see much in here. It has
implications for code which wants to do BUG while holding that lock..
> This patch also converts i386, x86-64 and powerpc to use this
> infrastructure. I have only tested i386; x86-64 and powerpc are not
> even compile-tested in this patch.
>
> Because powerpc also records the function name, I added this to i386
> and x86-64 for consistency. Strictly speaking the function name is
> redundant with kallsyms, so perhaps it can be dropped from powerpc.
I agree that the function name is a rather gratuitous space-consumer.
> +#ifdef CONFIG_GENERIC_BUG
> + /* Support for BUG */
> + struct list_head bug_list;
> + struct bug_entry *bug_table;
> + unsigned num_bugs;
Shouldn't this be u64? ;)
next parent reply other threads:[~2006-09-28 23:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060928225444.439520197@goop.org>
[not found] ` <20060928225452.229936605@goop.org>
2006-09-28 23:32 ` Andrew Morton [this message]
2006-09-28 23:43 ` [PATCH RFC 1/4] Generic BUG handling Jeremy Fitzhardinge
2006-09-29 0:07 ` Andrew Morton
2006-09-29 5:07 ` Michael Ellerman
2006-09-29 8:41 ` Jeremy Fitzhardinge
2006-09-29 8:49 ` Michael Ellerman
2006-09-29 8:52 ` Andrew Morton
2006-09-29 19:44 ` Jeremy Fitzhardinge
2006-09-29 19:54 ` Andrew Morton
2006-09-29 8:57 ` Andi Kleen
2006-09-29 9:10 ` Andrew Morton
2006-09-29 9:13 ` Andi Kleen
2006-09-29 9:18 ` Andrew Morton
2006-09-29 9:16 ` Andrew Morton
2006-09-29 9:33 ` Jeremy Fitzhardinge
2006-09-29 9:36 ` Jeremy Fitzhardinge
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=20060928163256.aa53b8d7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@muc.de \
--cc=hugh@veritas.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox