From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] 2.4.25: BUG(): Use guard page instead of page 0
Date: Thu, 04 Mar 2004 23:41:10 +0000 [thread overview]
Message-ID: <11811.1078443670@ocs3.ocs.com.au> (raw)
In-Reply-To: <20040218221302.GA87364@dragonfly.csd.sgi.com>
On Thu, 4 Mar 2004 16:25:00 -0700,
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>How about the following? I like the idea of using the guard page
>instead of address 0, but I sort of hate to add another magic number
>(though I guess you could argue that "0" is almost as magic as
>"0xa000000000000000").
Why not use 'break 0' for gcc < 3.1? No need to worry about which
pages are protected.
switch (break_num) {
case 0: /* unknown error (used by GCC for __builtin_abort()) */
die_if_kernel("bugcheck!", regs, break_num);
next prev parent reply other threads:[~2004-03-04 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 22:13 [PATCH] 2.4.25: BUG(): Use guard page instead of page 0 Jason Uhlenkott
2004-02-19 1:14 ` David Mosberger
2004-03-04 23:25 ` Bjorn Helgaas
2004-03-04 23:41 ` Keith Owens [this message]
2004-03-04 23:57 ` Bjorn Helgaas
2004-03-05 0:05 ` David Mosberger
2004-03-05 0:06 ` David Mosberger
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=11811.1078443670@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox