From: Hal Duston <hduston@speedscript.com>
To: linux-kernel@vger.kernel.org
Subject: Possible sparc64 signal handling issue
Date: 25 Jul 2003 15:17:10 -0500 [thread overview]
Message-ID: <1059164229.3926.16.camel@ulysseus> (raw)
In arch/sparc64/kernel/traps.c, data_access_exception() is defined to
receive 3 parameters, (and uses all three of them). In
arch/sparc64/kernel/unaligned.c it is only passed a single parameter.
This is causing me difficulty when handling segfault signals. On most
Linux platforms I have access to the siginfo_t.si_addr isn't populated
at all anyway, and I use the ucontext_t third parameter given to the
handler. Under sparc64 though, the third parameter doesn't point to
anything that I can discern, and due to the aforementioned three versus
one parameter issue, the value of si_addr in siginfo_t is incorrect as
well.
This issue appears to be present in both 2.4, and 2.6.
--
Hal Duston
hduston@speedscript.com
next reply other threads:[~2003-07-25 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 20:17 Hal Duston [this message]
2003-07-25 20:39 ` Possible sparc64 signal handling issue David S. Miller
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=1059164229.3926.16.camel@ulysseus \
--to=hduston@speedscript.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).