public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Garrett Cooper <yanegomi@gmail.com>
To: "K.D. Lucas" <kdlucas@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] ppoll01: add signal() syscall to register the signal handler
Date: Thu, 24 Sep 2009 22:24:34 -0700	[thread overview]
Message-ID: <364299f40909242224k55db7eaak8cc8b97e32d79788@mail.gmail.com> (raw)
In-Reply-To: <b9d696240909241328p25fdc8dcrac4f8bbfa4adad23@mail.gmail.com>

On Thu, Sep 24, 2009 at 1:28 PM, K.D. Lucas <kdlucas@gmail.com> wrote:
> I applied this patch, and it fixed ppoll01 on an Ubuntu Hardy box which had
> been failing. Kernel is 2.6.24.
>
> Kelly
>
> On Wed, Sep 23, 2009 at 11:59 PM, Chandru <chandru@in.ibm.com> wrote:
>>
>> The ppoll01 testcase has a signal handler in it but this signal handler is
>> not registered with the kernel through the signal() syscal. The testcase
>> fails when it sends a SIGINT to itself as part of one of the case of the
>> test run.
>> The following patch
>> 1. Adds a signal() syscall to register the signal handler
>> 2. Corrects the expected 'revents' for the case where ppoll() is called on
>> a file which is only opened in read/write mode, i.e case00.
>> 3. Takes away printing the type of error ( i.e strerror(errno) ) since it
>> only prints the last error seen and does not report the failures seen in the
>> cases before the last failed one. The reporting of NG or OK shoudl take care
>> of
>>    letting the user know the cases that have passed and cases that have
>> failed.
>>
>> Signed-off-by: Chandru S <chandru@linux.vnet.ibm.com>

...

>>                default:
>> -                               tst_resm(TFAIL, "%s failed - errno = %d :
>> %s", TCID, TEST_ERRNO, strerror(TEST_ERRNO));
>> +                               tst_resm(TFAIL, "%s failed", TCID);
>>                                RPRINTF("NG");
>>                                cleanup();
>>                                tst_exit();

Please don't change that line.
Thanks,
-Garrett

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; 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&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-09-25  5:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24  6:59 [LTP] [PATCH] ppoll01: add signal() syscall to register the signal handler Chandru
2009-09-24 20:28 ` K.D. Lucas
2009-09-25  5:24   ` Garrett Cooper [this message]
2009-09-26 11:25 ` Mike Frysinger
2009-10-01  7:27   ` Chandru
2009-10-01  8:16     ` Chandru
2009-10-01 16:39     ` Mike Frysinger

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=364299f40909242224k55db7eaak8cc8b97e32d79788@mail.gmail.com \
    --to=yanegomi@gmail.com \
    --cc=kdlucas@gmail.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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