From: Jeff Dike <jdike@addtoit.com>
To: Andrew Morton <akpm@osdl.org>
Cc: blaisorblade_spam@yahoo.it, bstroesser@fujitsu-siemens.com,
linux-arch@vger.kernel.org, jdike@ccure.user-mode-linux.org
Subject: Re: [PATCH 9/11] - UML - fix signal mask on delivery error
Date: Sun, 14 Nov 2004 17:13:17 -0500 [thread overview]
Message-ID: <200411142213.iAEMDHbV013050@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Fri, 12 Nov 2004 16:34:42 PST." <20041112163442.45fc966f.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
akpm@osdl.org said:
> Could you send one of the test apps? This is something which the arch
> maintainers might want to look into fixing, thanks.
Attached...
Included are
breakout.c - UML-specific breakouts, fixed in 2.6 and 2.4 now, but
please don't popularize these :-)
step_sighdlr.c - PTRACE_SINGLESTEPs into a signal handler, if I'm
reading the code right, fails on i386
interrupted_syscall.c - counts signals and system calls during
interrupted system calls, under ptrace and not. Fails on x86 under ptrace.
kernel_restorer.c - I can't get this to compile because it's too
intimate with the libc headers, expecting to get a k_sigaction from them.
sigmasking.c - Makes sure that when a signal is (not) delivered to
a bogus stack, that a segfault is delivered then, and not after returning
to userspace. This is the test relevant to the patch that Andrew replied
to.
Jeff
[-- Attachment #2: testtools-bodo-2004-10-29.tar --]
[-- Type: application/x-tar , Size: 40960 bytes --]
next prev parent reply other threads:[~2004-11-14 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200411130201.iAD210pT005889@ccure.user-mode-linux.org>
2004-11-13 0:34 ` [PATCH 9/11] - UML - fix signal mask on delivery error Andrew Morton
2004-11-14 22:13 ` Jeff Dike [this message]
2004-11-15 8:35 ` David Woodhouse
2004-11-22 15:30 ` David Woodhouse
2004-11-15 11:40 ` Bodo Stroesser
2004-11-15 17:18 ` Jeff Dike
2004-11-16 9:39 ` Bodo Stroesser
2004-11-30 14:59 ` David Woodhouse
2004-12-02 9:55 ` Bodo Stroesser
2004-12-02 11:25 ` Paul Mackerras
2004-12-02 11:40 ` Bodo Stroesser
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=200411142213.iAEMDHbV013050@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@ccure.user-mode-linux.org \
--cc=linux-arch@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