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 <[email protected]>
> Date: Tue, Aug 4, 2009 at 5:37 PM
> Subject: Re: Issue with rt_sigqueueinfo testcase in LTP.
> To: rohit verma <[email protected]>
> Cc: [email protected]
>
>
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to