Re: [FIX PATCHES] ltp-mq_unlink_speculative_7-2

On Tue, Jun 30, 2009 at 4:42 PM, Subrata
Modak<subrata@...> wrote:
> Hi Naresh,
>
> On Tue, 2009-06-30 at 13:12 +0530, naresh kamboju wrote:
>> Hi,
>>
>> I have noticed failure under open_posix_testsuite for
>> mq_unlink/speculative/7-2.c and fixed.
>> After changing the uninitialized to initialized char array of mqname[]
>> test case got PASSED.
>
> Great. Could you also please share with us the test results before and
> after this patch ?

Before patch Results:

conformance/interfaces/mq_unlink/speculative/7-2: execution: FAILED
# ./7-2.test
Test FAILED, error is Invalid argument

After patch Results:

conformance/interfaces/mq_unlink/speculative/7-2: execution: PASS
# ./7-2.test
Test PASSED

Best regards,
Naresh Kamboju

Re: [FIX PATCHES] ltp-mq_unlink_speculative_7-2

On Wed, 2009-07-01 at 14:16 +0530, naresh kamboju wrote:
> On Tue, Jun 30, 2009 at 4:42 PM, Subrata
> Modak<subrata@...> wrote:
> > Hi Naresh,
> >
> > On Tue, 2009-06-30 at 13:12 +0530, naresh kamboju wrote:
> >> Hi,
> >>
> >> I have noticed failure under open_posix_testsuite for
> >> mq_unlink/speculative/7-2.c and fixed.
> >> After changing the uninitialized to initialized char array of mqname[]
> >> test case got PASSED.
> >
> > Great. Could you also please share with us the test results before and
> > after this patch ?
> 
> Before patch Results:
> 
> conformance/interfaces/mq_unlink/speculative/7-2: execution: FAILED
> # ./7-2.test
> Test FAILED, error is Invalid argument
> 
> After patch Results:
> 
> conformance/interfaces/mq_unlink/speculative/7-2: execution: PASS
> # ./7-2.test
> Test PASSED

Thanks. What better way to start July to checkin your patch.

[ANNOUNCE] The Linux Test Project has been Released for JUNE 2009

Dear All,

The Linux Test Project test suite has been released for the month of
JUNE 2009. Please see ltp/INSTALL file carefully, as, there has been
multiple changes for building/installing the test suite.

The latest version of the test-suite contains 3000+ tests for the Linux
OS and can be found at:
http://ltp.sourceforge.net/,
Latest happenings in LTP can also be found at:
http://ltp.sourceforge.net/wiki/,
http://ltp.sourceforge.net/wikiArchives.php, and,
IRC: irc.freenode.org #ltp.

========================
JUNE 2009 Highlights:
========================
* Addition of 6 testcases for 5 new system calls,
* Major fixes for all new syscall tests,
* Major fixes for Power Management tests,
* Fixes for numerous other tests,
------------------------------

==============================
JUNE 2009 LTP Contributors:
==============================
* Manas Kumar Nayak,
* Márton Németh,
* Francesco Rundo,
* Cyril Hrubis,

Re: [FIX PATCHES] ltp-mq_unlink_speculative_7-2

>> >> After changing the uninitialized to initialized char array of mqname[]
>> >> test case got PASSED.
>> >

>> After patch Results:
>>
>> conformance/interfaces/mq_unlink/speculative/7-2: execution: PASS
>> # ./7-2.test
>> Test PASSED
>
> Thanks. What better way to start July to checkin your patch.

Great News
Thank you... 

Best Regards
Naresh Kamboju

>
> Regards--
> Subrata
>
>>
>>
>> Best regards,
>> Naresh Kamboju
>>
>> >
>> >>
>> >>

[PATCH] Fix pidns14 test case

[PATCH] pidns14

Container-init may be immune to unhandled fatal signals (like SIGUSR1)
even if they are from ancestor namespace. SIGKILL/SIGSTOP are the only
reliable signals to a container-init from ancestor namespace. Make sure
that container-init will not respond to signals other than
SIGKILL/SIGSTOP

Signed-off-by: M. Mohan Kumar <mohan@...>
---
 testcases/kernel/containers/pidns/pidns14.c |   13 +++++++------
 1 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/testcases/kernel/containers/pidns/pidns14.c b/testcases/kernel/containers/pidns/pidns14.c
index e95bf95..41602cd 100644
--- a/testcases/kernel/containers/pidns/pidns14.c
+++ b/testcases/kernel/containers/pidns/pidns14.c
 <at>  <at>  -67,9 +67,8  <at>  <at>  int child_fn(void *ttype)
 		tst_resm(TBROK, "pidns is not created.");
 		cleanup();
 	}
-	pause();
-	tst_resm(TFAIL, "Oops! Container init resumed after receiving SIGUSR1");
-	return -1;
+	sleep(10);
+	return 0;
 }

 /*
 <at>  <at>  -111,9 +110,11  <at>  <at>  int main(int argc, char *argv[])

(no subject)

It looks like the io_*.sh files are now not needed since the test source has been modified to check for an
autoconf definition.
This patch modifies the syscalls runtest file to call those test directly. (io_cancel, io_destroy01,
io_getevents01, 
io_setup01, io_submit01)

As the scripts are not needed any more, can we remove the following?

ltp/testcases/kernel/syscalls/io_cancel01.sh
ltp/testcases/kernel/syscalls/io_destroy01.sh
ltp/testcases/kernel/syscalls/io_getevents0101.sh
ltp/testcases/kernel/syscalls/io_setup01.sh
ltp/testcases/kernel/syscalls/io_submit01.sh

These scripts were not being copied into testcases/bin anyway and so AFAIK, did not run correctly by pan anyway.

Henry Yei
MontaVista Software, Inc.
hyei@...

 

------------------------------------------------------------------------------

_______________________________________________
Ltp-list mailing list
Ltp-list@...

[PATCH] Fix eventfd2_03 build failure on powerpc architecture

Hi, 

I've found a failure when building ltp-full-20090630 on powerpc:

eventfd2_03.c:48:2: error: #error Cannot detect your architecture!
eventfd2_03.c: In function ‘eventfd2’:
eventfd2_03.c:54: error: ‘__NR_eventfd2’ undeclared (first use in this function)
eventfd2_03.c:54: error: (Each undeclared identifier is reported only once
eventfd2_03.c:54: error: for each function it appears in.)
eventfd2_03.c: In function ‘main’:
eventfd2_03.c:129: warning: implicit declaration of function ‘waitpid’
make[4]: *** [eventfd2_03] Error 1
make[4]: Leaving directory `/root/ltp-full-20090630/testcases/kernel/syscalls/eventfd2'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/root/ltp-full-20090630/testcases/kernel/syscalls'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/ltp-full-20090630/testcases/kernel'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/ltp-full-20090630/testcases'
make: *** [all] Error 2

This patch fixes the failure, the test program identifier and 
adds a kernel version check.

Signed-off-by Lucio Correia <ljhc <at> br.ibm.com>

diff -Nurp ltp-full-20090630/testcases/kernel/include/powerpc64.in ltp-full-20090630.new/testcases/kernel/include/powerpc64.in
--- ltp-full-20090630/testcases/kernel/include/powerpc64.in	2008-12-12 13:13:18.000000000 -0200
+++ ltp-full-20090630.new/testcases/kernel/include/powerpc64.in	2009-07-01
18:35:52.000000000 -0300

[PATCH][syscalls] change io_* testcases to run directly

Again, I forgot the subject..

It looks like the io_*.sh files are now not needed since the test source has been modified to check for an
autoconf definition.
This patch modifies the syscalls runtest file to call those test directly. (io_cancel, io_destroy01,
io_getevents01, io_setup01, io_submit01)

As the scripts are not needed any more, can we remove the following?

ltp/testcases/kernel/syscalls/io_cancel01.sh
ltp/testcases/kernel/syscalls/io_destroy01.sh
ltp/testcases/kernel/syscalls/io_getevents0101.sh
ltp/testcases/kernel/syscalls/io_setup01.sh
ltp/testcases/kernel/syscalls/io_submit01.sh

These scripts were not being copied into testcases/bin anyway and so AFAIK, were not being run correctly by
pan anyway.

Henry Yei
MontaVista Software, Inc.
hyei@...

 

------------------------------------------------------------------------------

_______________________________________________

Re: Issue observed with chmod05, fchmod05 test cases

Wei Yongjun wrote:

>> ------------------------------------------------------------
>>
>> Should we treat this as Test case issue or kernel bug?
> 
> The different of 'nobody' and 'bin' is bin->GID has the CAP_FSETID 
> capability, but nobody->GID has not, I think.

I tried with a small program to check out the capabilities of bin and nobody couldn't find 
any difference

This is what I tried
Program I used
------------------------------
int main()
{
	cap_t cap = cap_get_proc();
	printf("Running with uid %d\n", getuid());
	printf("Running with capabilities: %s\n", cap_to_text(cap, NULL));
	cap_free(cap);
	return 0;
}
------------------------------
Running the program under different user gave same information

mx3455a:/home/sharyathi # su bin
bin <at> mx3455a:/home/sharyathi> ./a.out
Running with uid 1
Running with capabilities: =

getpeername01, getsockname01, socketpair01

Hi,

Can someone explain me why is in that subject tests for invalid pointer
choose
address 1 (or 7 in socketpair01)? I did some tests on Microblaze and for
this address I am getting segfault.
That's the reason why I think that problem is in glibc or ltp test. All
tests test reaction for invalid pointer address.

The interesting is that any address from 1 to 999 9999 caused segfault.
Address above not.
Below is memory map but first segment starts at 0x1000 0000 not 1000
0000 which is in patches below and works.

# cat /proc/66/maps
10000000-10001000 r-xp 00000000 00:01 394        /opcoded
10001000-10002000 rw-p 00000000 00:01 394        /opcoded
48000000-4801c000 r-xp 00000000 00:01 389        /lib/ld-2.3.3.so
4801c000-4801e000 rw-p 0001b000 00:01 389        /lib/ld-2.3.3.so
4801e000-4817c000 r-xp 00000000 00:01 379        /lib/libc-2.3.3.so
4817c000-4817f000 r--p 0015d000 00:01 379        /lib/libc-2.3.3.so
4817f000-48181000 rw-p 00160000 00:01 379        /lib/libc-2.3.3.so
48181000-48186000 rw-p 00000000 00:00 0
bfc15000-bfc2a000 rwxp 00000000 00:00 0          [stack]

Below are my changes which jump over segfault but they are still invalid
pointer.
Has someone ever met with this problem before?

Patches below are on this link too.