From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
linux-arch@vger.kernel.org, JANAK DESAI <janak@us.ibm.com>,
Ulrich Drepper <drepper@redhat.com>,
David Howells <dhowells@redhat.com>,
Davide Libenzi <davidel@xmailserver.org>,
Christoph Lameter <christoph@lameter.com>
Subject: Re: new syscalls
Date: Thu, 19 Jan 2006 08:53:07 +1100 [thread overview]
Message-ID: <1137621188.30084.67.camel@localhost.localdomain> (raw)
In-Reply-To: <20060118133629.1cda96fd.akpm@osdl.org>
On Wed, 2006-01-18 at 13:36 -0800, Andrew Morton wrote:
> That's an excellent point.
>
> Guys, architecture maintainers need test suites to verify that the syscalls
> actually work as they wire them up. Please share. A stable URL would be
> preferred - something which can go into the changlog or conceivably into
> the kernel source.
http://david.woodhou.se/sigmasking.c is a good one for testing
sigsuspend after hooking up TIF_RESTORE_SIGMASK stuff and the generic
sys_rt_sigsuspend(), although it's not actually my code. There were a
bunch of other tests in a tarball with that (on linux-arch a year or two
ago) which arch maintainers should also use occasionally when they play
with signal or ptrace code.
When I get back home I'll tidy up and publish the hacks I used for
testing pselect() and ppoll() so that those can be tested without
actually rebuilding glibc.
--
dwmw2
next prev parent reply other threads:[~2006-01-18 21:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 18:55 new syscalls Luck, Tony
2006-01-18 21:36 ` Andrew Morton
2006-01-18 21:48 ` Ulrich Drepper
2006-01-18 21:58 ` David S. Miller
2006-01-18 21:53 ` David Woodhouse [this message]
2006-01-18 21:58 ` David S. Miller
2006-01-20 10:04 ` Andi Kleen
2006-01-20 10:15 ` David S. Miller
2006-01-23 6:44 ` David Woodhouse
2006-01-23 9:58 ` Heiko Carstens
2006-01-19 1:17 ` Davide Libenzi
2006-01-19 1:26 ` David S. Miller
2006-01-19 5:00 ` David Woodhouse
2006-01-19 1:28 ` Andrew Morton
2006-01-19 21:48 ` Davide Libenzi
2006-01-20 0:13 ` Davide Libenzi
2006-01-20 0:23 ` Ulrich Drepper
2006-01-20 0:34 ` Davide Libenzi
2006-01-19 1:19 ` Christoph Lameter
2006-01-19 2:30 ` Andi Kleen
2006-01-19 13:50 ` JANAK DESAI
2006-01-22 17:45 ` JANAK DESAI
2006-01-24 23:44 ` JANAK DESAI
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 3:29 Andrew Morton
2006-01-18 3:38 ` Andi Kleen
2006-01-20 9:43 ` Heiko Carstens
2006-01-20 9:48 ` Andi Kleen
2006-01-20 9:49 ` 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=1137621188.30084.67.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=davidel@xmailserver.org \
--cc=dhowells@redhat.com \
--cc=drepper@redhat.com \
--cc=janak@us.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=tony.luck@intel.com \
/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