public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] 2.4.25: BUG(): Use guard page instead of page 0
Date: Fri, 05 Mar 2004 00:05:31 +0000	[thread overview]
Message-ID: <16455.50251.62626.925964@napali.hpl.hp.com> (raw)
In-Reply-To: <20040218221302.GA87364@dragonfly.csd.sgi.com>

>>>>> On Thu, 4 Mar 2004 16:57:43 -0700, Bjorn Helgaas <bjorn.helgaas@hp.com> said:

  Bjorn> On Thursday 04 March 2004 4:41 pm, Keith Owens wrote:

  >> 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);

  Bjorn> Sounds reasonable to me, but I'm too chicken.  Propose a
  Bjorn> patch and get David to take it, and I'll put it in 2.4.

I don't think it's worth changing (2.9x is out for 2.6 anyhow, and I
doubt anyone is using GCC 3.0 for real work; if you do, you're
probably in lots of trouble for other reasons!).  Besides, one
disadvantage of using "break 0" is that it will make Ski stop
immediately, which isn't what you want.

	--david

  parent reply	other threads:[~2004-03-05  0:05 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
2004-03-04 23:57 ` Bjorn Helgaas
2004-03-05  0:05 ` David Mosberger [this message]
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=16455.50251.62626.925964@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.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