Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Impossible fixup in do_ade
Date: Sun, 21 Sep 2003 09:00:33 -0700	[thread overview]
Message-ID: <20030921160033.GA31814@linux-mips.org> (raw)
In-Reply-To: <20030920152036.GA12905@nevyn.them.org>

On Sat, Sep 20, 2003 at 11:20:36AM -0400, Daniel Jacobowitz wrote:

> Here's a snippet from emulate_load_store_insn.  See the way the sdl and sdr
> are wrapped in fixups?  Well, the fixups can't trigger: we get to
> emulate_load_store_insn a second time, and we hit the fact that sdl_op has a
> "goto sigbus" before we hit the fixup_exception call.
> 
> It doesn't much matter, the bug I'm working on is whatever caused the first
> call.  But we get a SIGBUS when arguably we ought to get a SIGSEGV.

The fixup can be triggered - think of an missaligned load or store
inside the kernel itself.  If there's no fixup we'll simply assume the
instruction was in userspace and send a signal which is true unless there's
a kernel bug.

In case we deliver a signal at fault: I think it's arguable what signal is
the most appropriate one but for simplicity I decieded to consider the
address error exception as the cause so SIGBUS is the right signal.  We
simply don't gather sufficient information to deciede what the right
signal to send is and it's a very rare case anyway so nobody noticed yet :)

  Ralf

      reply	other threads:[~2003-09-22 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-20 15:20 Impossible fixup in do_ade Daniel Jacobowitz
2003-09-21 16:00 ` Ralf Baechle [this message]

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=20030921160033.GA31814@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dan@debian.org \
    --cc=linux-mips@linux-mips.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