public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] New test : sniperkill - killing processes from a distance
Date: Mon, 26 Oct 2009 22:33:06 +0530	[thread overview]
Message-ID: <1256576586.4929.60.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <364299f40910202206m10020bdg389ee8ab5994a488@mail.gmail.com>

On Tue, 2009-10-20 at 22:06 -0700, Garrett Cooper wrote: 
> Hi all,
>     The LTP signal tests are wonderful, but due to issues in our
> architecture, there were some unforeseen problems with some signal
> handling. As such I came up with a test and a C app named `sniperkill'
> and `killme.c'. sniperkill invokes killme according to a set matrix of
> signal numbers, according to the signal(7) manpage, verifying that the
> signal 1) terminates, 2) is ignored, or 3) is terminated producing a
> coredump. This also exercises the RT signals as well as the standard
> POSIX and Linux signals.
>     I verified the results on x86 and they were functional (minus
> SIGSYS which coredumped unexpectedly -- which means I get to file a
> bug with kernel.org -- yay!). I penciled in the other architectures as
> per the manpage, given that the other architectures we test on are
> clearly mentioned, I'm almost positive the data's in the correct
> spots, despite the ambiguity in the statement: `the first one is
> usually valid for alpha and sparc'.
>     I'm going to try running it on mips* and ppc, but the results
> won't be 100% sane with our OS platform (I know -- that's why wrote
> the test :(...).
>     An example log of my execution on x86_64 is included.
>     Please let me know if I should add this and where I should add
> this, so I can check it into the repo and more can benefit from this
> post-mortem analysis signal tool :).
> Thanks,
> -Garrett

Hey Garret. I feel it should go to a place where it signifies more:
testcases/kernel/syscalls/kill/

Regards--
Subrata

> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-10-26 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21  5:06 [LTP] New test : sniperkill - killing processes from a distance Garrett Cooper
2009-10-26 17:03 ` Subrata Modak [this message]
2009-10-29 18:32   ` Subrata Modak

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=1256576586.4929.60.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=yanegomi@gmail.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