From: Michal Simek <michal.simek@petalogix.com>
To: rohit verma <rohit.170309@gmail.com>
Cc: ltp-list <ltp-list@lists.sf.net>
Subject: Re: [LTP] Issue with rt_sigqueueinfo testcase in LTP.
Date: Thu, 06 Aug 2009 11:10:19 +0200 [thread overview]
Message-ID: <4A7A9DFB.7050305@petalogix.com> (raw)
In-Reply-To: <d51f89b0908040516i7c65740bi3e30e0972c8374fa@mail.gmail.com>
I can confirm that fault too - on Microblaze and x86 too.
The funny thing is that this test failed but it is reported as passed in
log.
Michal
> FYI...
>
>
> ---------- Forwarded message ----------
> From: Subrata Modak <subrata@linux.vnet.ibm.com>
> Date: Tue, Aug 4, 2009 at 5:37 PM
> Subject: Re: Issue with rt_sigqueueinfo testcase in LTP.
> To: rohit verma <rohit.170309@gmail.com>
> Cc: maknayak@in.ibm.com
>
>
> Hi Rohit,
>
> On Tue, 2009-08-04 at 11:40 +0530, rohit verma wrote:
>
>> Dear Manas Kumar Nayak,
>>
>> I have found an issue with rt_sigqueueinfo test-case.
>>
>> Following is the test output:
>>
>> rt_sigqueueinfo01 1 PASS : Test Succeeded
>> rt_sigqueueinfo01 1 FAIL : Test Failed, errno=1 : Operation not permitted
>> rt_sigqueueinfo01 1 PASS : Test Succeeded
>> rt_sigqueueinfo01 1 FAIL : Test Failed, errno=1 : Operation not permitted
>> rt_sigqueueinfo01 0 WARN : tst_rmdir(): rmobj(/tmp/rt_3FaSpK)
>> failed: lstat(/tmp/rt_3FaSpK) failed; errno=2: No such file or
>> directory
>>
>> I think the following lines are causing the failures:
>>
>> (Line - 164)
>>
>> uinfo.si_errno = 0;
>> uinfo.si_code = 0;//SI_USER
>> TEST(retval = syscall(__NR_rt_sigqueueinfo, getpid(), 17, &uinfo));
>>
>> Reason -
>>
>> You can observe the following comment & source when you look at the
>> Linux source (v 2.6.29)
>> (linux-2.6.29/kernel/signal.c)
>>
>> /* Not even root can pretend to send signals from the kernel.
>> Nor can they impersonate a kill(), which adds source info. */
>> if (info.si_code >= 0)
>> return -EPERM;
>>
>> which implies that si_code cannot be set to ' 0 ' (SI_USER) when
>> invoking the rt_sigqueueinfo syscall.
>>
>>
>> I am not sure how to fix this issue. But, a possible fix would be to
>> remove the second set of fork &
>> rt_sigqueueinfo invocations and use the first set (with SI_QUEUE). If
>> needed, the loop count can be
>> increased.
>>
>
> Please propose this over to the mailing list. Manas has just ported the
> test case from Crackerjack to LTP. He may not be exactly aware of the
> issues, as it was a blind port, which in one way was good, as the
> porting generated issues, people interested discussed and solved
> them ;-)
>
> Regards--
> Subrata
>
>
>>
>
>
>
>
>
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-08-06 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d51f89b0908032310k20c3843am7ea069d03436a7a@mail.gmail.com>
[not found] ` <1249387637.15587.29.camel@subratamodak.linux.ibm.com>
2009-08-04 12:16 ` [LTP] Issue with rt_sigqueueinfo testcase in LTP rohit verma
2009-08-06 9:10 ` Michal Simek [this message]
2009-08-07 0:50 ` [LTP] [PATCH] " Henry Yei
2009-08-07 2:21 ` Garrett Cooper
2009-08-07 12:41 ` Subrata Modak
2009-08-14 6:55 ` rohit verma
2009-08-14 18:39 ` Henry Yei
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=4A7A9DFB.7050305@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=ltp-list@lists.sf.net \
--cc=rohit.170309@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