[LTP] [00/12 FAILURE] Reporting LTP run issues on Fedora 13 ppc6

[LTP] [00/12 FAILURE] Reporting LTP run issues on Fedora 13 ppc6

[Subrata Modak]

Hi,

Recently i did a ltprunall on my Fedora 13 system running on PPC64 box,
and came across some failures/issues. I want to report them to you to
know whether you also have observed similar issues on either PPC64, or
systems that matter to you.

Probably, i am trying to find out whether they are test case issues, or,
issues with the kernel. If they turn out to be testcase issues, then we
would need to fix them quit soon :-)

Since i was not looking into all LTP mails for the last couple of months,
may be some of these issues might have been reported and fixed proposed.
I would apolozise for the noise again.

My system configuration:
[root@mjs22lp1 ~]# uname -a
Linux 2.6.33.1-19.fc13.ppc64 #1 SMP Tue Mar 23 06:32:38 EDT 2010 ppc64 ppc64 ppc64 GNU/Linux
[root@mjs22lp1 ~]# cat /etc/issue
Fedora release 13 (Goddard)
Kernel \r on an \m (\l)

Regards--
Subrata


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[01/12 FAILURE] LTPX Memory CGROUP test creates Call Trace and Badness at mm/oom_kill.c:393

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 14512 bytes --]

Subject: LTP�� Memory CGROUP test creates Call Trace & Badness at mm/oom_kill.c:393

Issues Description Below:
===========================

# ./runltp -f memcg_control

You will see the following /var/log/messages entry:
***********************************************************************************************
Apr 22 23:16:42 mjs22lp1 kernel: memcg_control_t invoked oom-killer:
gfp_mask=0xd0, order=0, oom_adj=0
Apr 22 23:16:42 mjs22lp1 kernel: memcg_control_t invoked oom-killer:
gfp_mask=0xd0, order=0, oom_adj=0
Apr 22 23:16:42 mjs22lp1 kernel: memcg_control_t cpuset=/ mems_allowed=0-255
Apr 22 23:16:42 mjs22lp1 kernel: Call Trace:
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8b520] [c0000000000161c8]
.show_stack+0xb0/0x1a0
Apr 22 23:16:42 mjs22lp1 kernel: memcg_control_t cpuset=/ mems_allowed=0-255
Apr 22 23:16:42 mjs22lp1 kernel: Call Trace:
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83520] [c0000000000161c8]
.show_stack+0xb0/0x1a0 (unreliable)
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec835e0] [c000000000735358]
.dump_stack+0x28/0x3c
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83660] [c000000000194700]
.dump_header+0xa8/0x1e0
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83720] [c0000000001948b8]
.oom_kill_process+0x80/0x194
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec837e0] [c000000000195348]
.mem_cgroup_out_of_memory+0x88/0xc0
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83890] [c0000000001ec750]
.__mem_cgroup_try_charge+0x21c/0x320
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83990] [c0000000001ed258]
.mem_cgroup_charge_common+0x84/0xd8
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83a60] [c0000000001ed334]
.mem_cgroup_newpage_charge+0x88/0xbc
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83b00] [c0000000001b57c0]
.do_wp_page+0x6f8/0x9e4
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83bf0] [c0000000001b77e0]
.handle_mm_fault+0x834/0x8d8
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83cf0] [c000000000731ce0]
.do_page_fault+0x434/0x65c
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83e30] [c0000000000056cc]
handle_page_fault+0x20/0x74
Apr 22 23:16:42 mjs22lp1 kernel: Task in /1/sub killed as a result of limit of
/1
Apr 22 23:16:42 mjs22lp1 kernel: (unreliable)
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8b5e0] [c000000000735358]
.dump_stack+0x28/0x3c
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8b660] [c000000000194700]
.dump_header+0xa8/0x1e0
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8b720] [c0000000001948b8]
.oom_kill_process+0x80/0x194
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8b7e0] [c000000000195348]
.mem_cgroup_out_of_memory+0x88/0xc0
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8b890] [c0000000001ec750]
.__mem_cgroup_try_charge+0x21c/0x320
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8b990] [c0000000001ed258]
.mem_cgroup_charge_common+0x84/0xd8
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8ba60] [c0000000001ed334]
.mem_cgroup_newpage_charge+0x88/0xbc
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8bb00] [c0000000001b57c0]
.do_wp_page+0x6f8/0x9e4
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8bbf0] [c0000000001b77e0]
.handle_mm_fault+0x834/0x8d8
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8bcf0] [c000000000731ce0]
.do_page_fault+0x434/0x65c
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003eb8be30] [c0000000000056cc]
handle_page_fault+0x20/0x74
Apr 22 23:16:42 mjs22lp1 kernel: Task in /1/sub killed as a result of limit of
/1
Apr 22 23:16:42 mjs22lp1 kernel: memory: usage 4kB, limit 4kB, failcnt 15
Apr 22 23:16:42 mjs22lp1 kernel: memory+swap: usage 4kB, limit 4kB, failcnt 0
Apr 22 23:16:42 mjs22lp1 kernel: Mem-Info:
Apr 22 23:16:42 mjs22lp1 kernel: Node 0 DMA per-cpu:
Apr 22 23:16:42 mjs22lp1 kernel: CPU    0: hi:  186, btch:  31 usd:  90
Apr 22 23:16:42 mjs22lp1 kernel: CPU    1: hi:  186, btch:  31 usd: 109
Apr 22 23:16:42 mjs22lp1 kernel: CPU    2: hi:  186, btch:  31 usd:  68
Apr 22 23:16:42 mjs22lp1 kernel: CPU    3: hi:  186, btch:  31 usd: 121
Apr 22 23:16:42 mjs22lp1 kernel: CPU    4: hi:  186, btch:  31 usd: 134
Apr 22 23:16:42 mjs22lp1 kernel: CPU    5: hi:  186, btch:  31 usd: 125
Apr 22 23:16:42 mjs22lp1 kernel: CPU    6: hi:  186, btch:  31 usd: 137
Apr 22 23:16:42 mjs22lp1 kernel: CPU    7: hi:  186, btch:  31 usd: 104
Apr 22 23:16:42 mjs22lp1 kernel: Node 1 DMA per-cpu:
Apr 22 23:16:42 mjs22lp1 kernel: CPU    0: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    1: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    2: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    3: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    4: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    5: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    6: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    7: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: active_anon:4373 inactive_anon:0
isolated_anon:0
Apr 22 23:16:42 mjs22lp1 kernel: active_file:28578 inactive_file:22728
isolated_file:0
Apr 22 23:16:42 mjs22lp1 kernel: unevictable:0 dirty:11 writeback:0 unstable:0
Apr 22 23:16:42 mjs22lp1 kernel: free:506114 slab_reclaimable:5173
slab_unreclaimable:33442
Apr 22 23:16:42 mjs22lp1 kernel: mapped:4419 shmem:44 pagetables:477 bounce:0
Apr 22 23:16:42 mjs22lp1 kernel: Node 0 DMA free:761980kB min:3060kB low:3824kB
high:4588kB active_anon:17492kB inactive_anon:0kB active_file:114312kB
inactive_file:90912kB unevictable:0kB isolated(anon):0kB isolated(file):0kB
present:1228160kB mlocked:0kB dirty:44kB writeback:0kB mapped:17664kB
shmem:176kB slab_reclaimable:19604kB slab_unreclaimable:121920kB
kernel_stack:3312kB pagetables:1908kB unstable:0kB bounce:0kB writeback_tmp:0kB
pages_scanned:0 all_unreclaimable? no
Apr 22 23:16:42 mjs22lp1 kernel: lowmem_reserve[]: 0 0 0
Apr 22 23:16:42 mjs22lp1 kernel: Node 1 DMA free:1262476kB min:3344kB
low:4180kB high:5016kB active_anon:0kB inactive_anon:0kB active_file:0kB
inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB
present:1340416kB mlocked:0kB dirty:0kB writeback:0kB mapped:12kB shmem:0kB
slab_reclaimable:1088kB slab_unreclaimable:11848kB kernel_stack:64kB
pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0
all_unreclaimable? no
Apr 22 23:16:42 mjs22lp1 kernel: lowmem_reserve[]: 0 0 0
Apr 22 23:16:42 mjs22lp1 kernel: Node 0 DMA:
Apr 22 23:16:42 mjs22lp1 kernel: memory: usage 4kB, limit 4kB, failcnt 15
Apr 22 23:16:42 mjs22lp1 kernel: 6*4kB 7*8kB 3*16kB 2*32kB 1*64kB 7*128kB
10*256kB 3*512kB 3*1024kB 2*2048kB 3*4096kB 2*8192kB 44*16384kB = 761984kB
Apr 22 23:16:42 mjs22lp1 kernel: Node 1 DMA: 17*4kB
Apr 22 23:16:42 mjs22lp1 kernel: memory+swap: usage 4kB, limit 4kB, failcnt 0
Apr 22 23:16:42 mjs22lp1 kernel: 25*8kB 34*16kB 43*32kB 24*64kB 12*128kB
11*256kB 12*512kB 9*1024kB 9*2048kB 8*4096kB 5*8192kB 70*16384kB = 1262476kB
Apr 22 23:16:42 mjs22lp1 kernel: 51349 total pagecache pages
Apr 22 23:16:42 mjs22lp1 kernel: 0 pages in swap cache
Apr 22 23:16:42 mjs22lp1 kernel: Swap cache stats: add 0, delete 0, find 0/0
Apr 22 23:16:42 mjs22lp1 kernel: Free swap  = 9437160kB
Apr 22 23:16:42 mjs22lp1 kernel: Total swap = 9437160kB
Apr 22 23:16:42 mjs22lp1 kernel: Mem-Info:
Apr 22 23:16:42 mjs22lp1 kernel: Node 0 DMA per-cpu:
Apr 22 23:16:42 mjs22lp1 kernel: CPU    0: hi:  186, btch:  31 usd:  90
Apr 22 23:16:42 mjs22lp1 kernel: CPU    1: hi:  186, btch:  31 usd: 109
Apr 22 23:16:42 mjs22lp1 kernel: CPU    2: hi:  186, btch:  31 usd:  68
Apr 22 23:16:42 mjs22lp1 kernel: CPU    3: hi:  186, btch:  31 usd: 121
Apr 22 23:16:42 mjs22lp1 kernel: CPU    4: hi:  186, btch:  31 usd: 134
Apr 22 23:16:42 mjs22lp1 kernel: CPU    5: hi:  186, btch:  31 usd: 125
Apr 22 23:16:42 mjs22lp1 kernel: CPU    6: hi:  186, btch:  31 usd: 137
Apr 22 23:16:42 mjs22lp1 kernel: CPU    7: hi:  186, btch:  31 usd: 104
Apr 22 23:16:42 mjs22lp1 kernel: Node 1 DMA per-cpu:
Apr 22 23:16:42 mjs22lp1 kernel: CPU    0: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    1: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    2: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    3: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    4: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    5: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    6: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: CPU    7: hi:  186, btch:  31 usd:   0
Apr 22 23:16:42 mjs22lp1 kernel: active_anon:4373 inactive_anon:0
isolated_anon:0
Apr 22 23:16:42 mjs22lp1 kernel: active_file:28578 inactive_file:22728
isolated_file:0
Apr 22 23:16:42 mjs22lp1 kernel: unevictable:0 dirty:11 writeback:0 unstable:0
Apr 22 23:16:42 mjs22lp1 kernel: free:506114 slab_reclaimable:5173
slab_unreclaimable:33442
Apr 22 23:16:42 mjs22lp1 kernel: mapped:4419 shmem:44 pagetables:477 bounce:0
Apr 22 23:16:42 mjs22lp1 kernel: Node 0 DMA free:761980kB min:3060kB low:3824kB
high:4588kB active_anon:17492kB inactive_anon:0kB active_file:114312kB
inactive_file:90912kB unevictable:0kB isolated(anon):0kB isolated(file):0kB
present:1228160kB mlocked:0kB dirty:44kB writeback:0kB mapped:17664kB
shmem:176kB slab_reclaimable:19604kB slab_unreclaimable:121920kB
kernel_stack:3312kB pagetables:1908kB unstable:0kB bounce:0kB writeback_tmp:0kB
pages_scanned:0 all_unreclaimable? no
Apr 22 23:16:42 mjs22lp1 kernel: lowmem_reserve[]: 0 0 0
Apr 22 23:16:42 mjs22lp1 kernel: Node 1 DMA free:1262476kB min:3344kB
low:4180kB high:5016kB active_anon:0kB inactive_anon:0kB active_file:0kB
inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB
present:1340416kB mlocked:0kB dirty:0kB writeback:0kB mapped:12kB shmem:0kB
slab_reclaimable:1088kB slab_unreclaimable:11848kB kernel_stack:64kB
pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0
all_unreclaimable? no
Apr 22 23:16:42 mjs22lp1 kernel: lowmem_reserve[]: 0 0 0
Apr 22 23:16:42 mjs22lp1 kernel: Node 0 DMA: 6*4kB 7*8kB 3*16kB 2*32kB 1*64kB
7*128kB 10*256kB 3*512kB 3*1024kB 2*2048kB 3*4096kB 2*8192kB 44*16384kB =
761984kB
Apr 22 23:16:42 mjs22lp1 kernel: Node 1 DMA: 17*4kB 25*8kB 34*16kB 43*32kB
24*64kB 12*128kB 11*256kB 12*512kB 9*1024kB 9*2048kB 8*4096kB 5*8192kB
70*16384kB = 1262476kB
Apr 22 23:16:42 mjs22lp1 kernel: 51349 total pagecache pages
Apr 22 23:16:42 mjs22lp1 kernel: 0 pages in swap cache
Apr 22 23:16:42 mjs22lp1 kernel: Swap cache stats: add 0, delete 0, find 0/0
Apr 22 23:16:42 mjs22lp1 kernel: Free swap  = 9437160kB
Apr 22 23:16:42 mjs22lp1 kernel: Total swap = 9437160kB
Apr 22 23:16:42 mjs22lp1 kernel: 966656 pages RAM
Apr 22 23:16:42 mjs22lp1 kernel: 33079 pages reserved
Apr 22 23:16:42 mjs22lp1 kernel: 80979 pages shared
Apr 22 23:16:42 mjs22lp1 kernel: 170832 pages non-shared
Apr 22 23:16:42 mjs22lp1 kernel: Memory cgroup out of memory: kill process 1738
(memcg_control_t) score 131 or a child
Apr 22 23:16:42 mjs22lp1 kernel: Killed process 1743 (memcg_control_t)
vsz:5628kB, anon-rss:156kB, file-rss:12kB
Apr 22 23:16:42 mjs22lp1 kernel: VM: killing process memcg_control_t
Apr 22 23:16:42 mjs22lp1 kernel: 966656 pages RAM
Apr 22 23:16:42 mjs22lp1 kernel: 33079 pages reserved
Apr 22 23:16:42 mjs22lp1 kernel: 80822 pages shared
Apr 22 23:16:42 mjs22lp1 kernel: 170835 pages non-shared
Apr 22 23:16:42 mjs22lp1 kernel: ------------[ cut here ]------------
Apr 22 23:16:42 mjs22lp1 kernel: Badness at mm/oom_kill.c:393
Apr 22 23:16:42 mjs22lp1 kernel: NIP: c0000000001942f0 LR: c0000000001942e0
CTR: 0000000000000001
Apr 22 23:16:42 mjs22lp1 kernel: REGS: c00000003ec83400 TRAP: 0700   Tainted: G
       W   (2.6.33.1-19.fc13.ppc64)
Apr 22 23:16:42 mjs22lp1 kernel: MSR: 8000000000029032 <EE,ME,CE,IR,DR>  CR:
24224422  XER: 00000000
Apr 22 23:16:42 mjs22lp1 kernel: TASK = c00000004e230000[1743]
'memcg_control_t' THREAD: c00000003ec80000 CPU: 7
Apr 22 23:16:42 mjs22lp1 kernel: GPR00: c0000000001942e0 c00000003ec83680
c000000001329558 0000000000000001
Apr 22 23:16:42 mjs22lp1 kernel: GPR04: c00000004d8259c8 000000000000000c
0000000000000000 0000000000000002
Apr 22 23:16:42 mjs22lp1 kernel: GPR08: 0000000000000000 0000000000000000
0000000000000934 000000000000079b
Apr 22 23:16:42 mjs22lp1 kernel: GPR12: 0000000024224484 c00000000135c300
0000000000000000 00000000100f0000
Apr 22 23:16:42 mjs22lp1 kernel: GPR16: 00000000100f4a54 0000000046ba0093
c00000004e0410d8 f000000000cdcaa8
Apr 22 23:16:42 mjs22lp1 kernel: GPR20: c00000004e041058 c00000004e041068
c00000003ec83900 0000000000000000
Apr 22 23:16:42 mjs22lp1 kernel: GPR24: c000000000c7dd10 c00000000095e4aa
00000000000000d0 0000000000000000
Apr 22 23:16:42 mjs22lp1 kernel: GPR28: c00000004d8259b0 c00000004d824f80
c0000000012a4f68 c00000003ec83680
Apr 22 23:16:42 mjs22lp1 kernel: NIP [c0000000001942f0]
.__oom_kill_task+0x74/0x15c
Apr 22 23:16:42 mjs22lp1 kernel: LR [c0000000001942e0]
.__oom_kill_task+0x64/0x15c
Apr 22 23:16:42 mjs22lp1 kernel: Call Trace:
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83680] [c0000000001942e0]
.__oom_kill_task+0x64/0x15c (unreliable)
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83720] [c000000000194940]
.oom_kill_process+0x108/0x194
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec837e0] [c000000000195348]
.mem_cgroup_out_of_memory+0x88/0xc0
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83890] [c0000000001ec750]
.__mem_cgroup_try_charge+0x21c/0x320
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83990] [c0000000001ed258]
.mem_cgroup_charge_common+0x84/0xd8
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83a60] [c0000000001ed334]
.mem_cgroup_newpage_charge+0x88/0xbc
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83b00] [c0000000001b57c0]
.do_wp_page+0x6f8/0x9e4
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83bf0] [c0000000001b77e0]
.handle_mm_fault+0x834/0x8d8
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83cf0] [c000000000731ce0]
.do_page_fault+0x434/0x65c
Apr 22 23:16:42 mjs22lp1 kernel: [c00000003ec83e30] [c0000000000056cc]
handle_page_fault+0x20/0x74
Apr 22 23:16:42 mjs22lp1 kernel: Instruction dump:
Apr 22 23:16:42 mjs22lp1 kernel: 0fe00000 e87e8000 485a1275 60000000 480000e4
3b9d0a30 7f83e378 4859aa69
Apr 22 23:16:42 mjs22lp1 kernel: 60000000 e93d0288 2fa90000 40be002c <0fe00000>
e87e8008 38bd04e8 e89d02b2
Apr 22 23:16:42 mjs22lp1 kernel: tried to kill an mm-less task 1738
(memcg_control_t)!
Apr 22 23:16:42 mjs22lp1 kernel: VM: killing process memcg_control_t
***********************************************************************************************

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[02/12 FAILURE] LTPX File Capabilities tests becomes defunct and does not complete beyond 12 hours

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 7011 bytes --]

Subject: LTP�� File Capabilities tests becomes defunct and does not complete beyond 12 hours

Issues Description Below:
===================================
I know Serge and Garret is already working on them and a considerable fix
is already in the pipeline.

# ./runltp -f filecaps
<<<test_start>>>
tag=Filecaps stime=1271951563
cmdline="filecapstest.sh"
contacts=""
analysis=exit
<<<test_output>>>
Running in:
cap_sys_admin tests
testing for correct caps
...
The test hangs here for more than 12 hours.

Following are various info about the processes running this test:
[root@alien5 ltp]# ps ajxf 
1608  1724  1608  1458 ?           -1 S        0   0:00  \_
/opt/ltp/bin/ltp-pan -e -S -a 1608 -n 1608 -p -f /tmp/ltp-71wskF3epE/alltests
-l /opt/ltp/results/LTP_RUN_ON-20
1724 30311 30311  1458 ?           -1 S        0   0:00      \_ /bin/sh
/opt/ltp/testcases/bin/filecapstest.sh
30311 30315 30311  1458 ?           -1 S        0   0:00          \_
verify_caps_exec 1
30315 30316 30311  1458 ?           -1 Z     1000   0:00              \_
[verify_caps_exe] <defunct>

STRACE on the PIDs does not show anything:
[root@alien5 ltp]# strace -p 30425
Process 30425 attached - interrupt to quit
waitpid(-1, ^C <unfinished ...>
Process 30425 detached
[root@alien5 ltp]# strace -p 30429
Process 30429 attached - interrupt to quit
open("caps_fifo", O_RDONLY^C <unfinished ...>
Process 30429 detached
[root@alien5 ltp]# strace -p 30430
attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted

[root@alien5 ltp]# getenforce
Permissive
[root@alien5 ltp]# tail -f /var/log/messages
2010-04-21T18:00:15.752320+05:18 alien5 setroubleshoot: SELinux is preventing
/sbin/rsyslogd access to a leaked/opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output file descriptor. For
complete SELinux messages. run sealert -l 894e0d2d-23c3-45d1-9108-71ad97f5a45e
2010-04-21T18:00:15.794214+05:18 alien5 setroubleshoot: SELinux is preventing
/sbin/rsyslogd access to a leaked
/opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output file descriptor. For
complete SELinux messages. run sealert -l 894e0d2d-23c3-45d1-9108-71ad97f5a45e
2010-04-21T18:00:15.823557+05:18 alien5 setroubleshoot: SELinux is preventing
/sbin/rsyslogd access to a leaked
/opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output file descriptor. For
complete SELinux messages. run sealert -l 894e0d2d-23c3-45d1-9108-71ad97f5a45e
2010-04-21T18:00:17.721361+05:18 alien5 syslogtst: syslogtst:10 error level is
logged
Apr 21 18:00:19 alien5 kernel: imklog 4.4.2, log source = /proc/kmsg started.
Apr 21 18:00:19 alien5 rsyslogd: [origin software="rsyslogd" swVersion="4.4.2"
x-pid="2165" x-info="http://www.rsyslog.com"] (re)start
Apr 21 18:00:20 alien5 setroubleshoot: SELinux is preventing /sbin/rsyslogd
access to a leaked /opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output
file descriptor. For complete SELinux messages. run sealert -l
894e0d2d-23c3-45d1-9108-71ad97f5a45e
Apr 21 18:00:20 alien5 setroubleshoot: SELinux is preventing /sbin/rsyslogd
access to a leaked /opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output
file descriptor. For complete SELinux messages. run sealert -l
894e0d2d-23c3-45d1-9108-71ad97f5a45e
Apr 21 18:00:20 alien5 setroubleshoot: SELinux is preventing /sbin/rsyslogd
access to a leaked /opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output
file descriptor. For complete SELinux messages. run sealert -l
894e0d2d-23c3-45d1-9108-71ad97f5a45e

So, i executed the following command:
[root@alien5 ltp]# sealert -l 894e0d2d-23c3-45d1-9108-71ad97f5a45e
exception when creating syslog handler: [Errno 2] No such file or directory
Summary:
SELinux is preventing /sbin/rsyslogd access to a leaked
/opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output file descriptor.

Detailed Description:

[rsyslogd has a permissive type (syslogd_t). This access was not denied.]

SELinux denied access requested by the rsyslogd command. It looks like this is
either a leaked descriptor or rsyslogd output was redirected to a file it is
not
allowed to access. Leaks usually can be ignored since SELinux is just closing
the leak and reporting the error. The application does not use the descriptor,
so it will run properly. If this is a redirection, you will not get output in
the /opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output. You should
generate a bugzilla on selinux-policy, and it will get routed to the
appropriate
package. You can safely ignore this avc.

Allowing Access:

You can generate a local policy module to allow this access - see FAQ
(http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385)

Additional Information:

Source Context                unconfined_u:system_r:syslogd_t:s0
Target Context                unconfined_u:object_r:usr_t:s0
Target Objects                /opt/ltp/output/LTP_RUN_ON-
                              2010_Apr_21-17h_51m_22s.output [ file ]
Source                        rsyslogd
Source Path                   /sbin/rsyslogd
Port                          <Unknown>
Host                          
Source RPM Packages           rsyslog-4.4.2-6.fc13
Target RPM Packages           
Policy RPM                    selinux-policy-3.7.15-4.fc13
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Plugin Name                   leaks
Host Name                     
Platform                      Linux 
                              2.6.33.1-19.fc13.ppc64 #1 SMP Tue Mar 23 06:32:38
                              EDT 2010 ppc64 ppc64
Alert Count                   186
First Seen                    Tue Apr 20 23:55:40 2010
Last Seen                     Wed Apr 21 18:00:19 2010
Local ID                      894e0d2d-23c3-45d1-9108-71ad97f5a45e
Line Numbers                  

Raw Audit Messages            

node= type=AVC msg=audit(1271853019.957:317): avc: 
denied  { append } for  pid=2164 comm="rsyslogd"
path="/opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.output" dev=sda3
ino=1188363 scontext=unconfined_u:system_r:syslogd_t:s0
tcontext=unconfined_u:object_r:usr_t:s0 tclass=file

node= type=AVC msg=audit(1271853019.957:317): avc: 
denied  { append } for  pid=2164 comm="rsyslogd"
path="/opt/ltp/results/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.log" dev=sda3
ino=1188362 scontext=unconfined_u:system_r:syslogd_t:s0
tcontext=unconfined_u:object_r:usr_t:s0 tclass=file

node= type=AVC msg=audit(1271853019.957:317): avc: 
denied  { append } for  pid=2164 comm="rsyslogd"
path="/opt/ltp/output/LTP_RUN_ON-2010_Apr_21-17h_51m_22s.failed" dev=sda3
ino=1188364 scontext=unconfined_u:system_r:syslogd_t:s0
tcontext=unconfined_u:object_r:usr_t:s0 tclass=file

node= type=SYSCALL msg=audit(1271853019.957:317):
arch=14 syscall=11 success=yes exit=0 a0=1026c900 a1=1026b5b0 a2=1026b640
a3=1026b5a8 items=0 ppid=2163 pid=2164 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0
egid=0 sgid=0 fsgid=0 tty=(none) ses=22 comm="rsyslogd" exe="/sbin/rsyslogd"
subj=unconfined_u:system_r:syslogd_t:s0 key=(null)

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[03/12 FAILURE] LTPX Memory Conroller test fails and hangs system for more than 12 hours

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2610 bytes --]

Subject: LTP�� Memory Conroller test fails and hangs system for more than 12 hours

Issue Description below:
==============================
# ./runltp -f test_controllers
TEST 1: MEMORY CONTROLLER TESTING
RUNNING SETUP.....
TEST STARTED: Please avoid using system while this test executes
Before task migration to group2
group2 memory usage: 0 Bytes
After task migration to group2
group2 memory usage: 0 Bytes
TPASS   Memory Resource Controller: Task Migration test 1 PASSED
Memory Resource Controller test executed successfully.
Cleanup called
/opt/ltp/testcases/bin/run_memctl_test.sh: line 87: [: -lt: unary operator
expected
TEST 2: MEMORY CONTROLLER TESTING
RUNNING SETUP.....
TEST STARTED: Please avoid using system while this test executes
Before task migration to group2
group2 memory usage: 0 Bytes
After task migration to group2 and doing malloc
group2 memory usage: 63045632 Bytes
TPASS   Memory Resource Controller: Task Migration test 2 PASSED
Memory Resource Controller test executed successfully.
Cleanup called
/opt/ltp/testcases/bin/run_memctl_test.sh: line 87: [: -lt: unary operator
expected
TEST 3: MEMORY CONTROLLER TESTING
RUNNING SETUP.....
TEST STARTED: Please avoid using system while this test executes
failcnt = 4498
TPASS   Memory Resource Controller: failcnt check test PASSED
Memory Resource Controller test executed successfully.
Cleanup called
/opt/ltp/testcases/bin/run_memctl_test.sh: line 87: [: -lt: unary operator
expected
TEST 4: MEMORY CONTROLLER TESTING
RUNNING SETUP.....
TEST STARTED: Please avoid using system while this test executes
TINFO   Memory Resource Controller: stat check test fails in first run
TFAIL   Memory Resource Controller: stat check test FAILED

Process infos are:
[root@mjs22lp1 ltp]# ps axjf
    1  1608  1608  1458 ?           -1 S        0   0:00 /bin/sh ./runltp -g
fc13_p6_kernel-2.6.33.1-19.fc13.ppc64_host-mjs22lp1_20100423_23:16:16.html
 1608  1724  1608  1458 ?           -1 S        0   0:00  \_
/opt/ltp/bin/ltp-pan -e -S -a 1608 -n 1608 -p -f /tmp/ltp-71wskF3epE/alltests
-l /opt/ltp/results/LTP_RUN_ON-20
 1724  1784  1784  1458 ?           -1 S        0   0:00      \_ /bin/bash
/opt/ltp/testcases/bin/test_controllers.sh
 1784 14666  1784  1458 ?           -1 S        0   0:00          \_ /bin/bash
/opt/ltp/testcases/bin/run_memctl_test.sh 4
14666 14682  1784  1458 ?           -1 R        0 733:20              \_
./memctl_task_1

Both strace and ltrace info does not wield any result:
[root@mjs22lp1 ltp]# strace -p 14682
Process 14682 attached - interrupt to quit
[root@mjs22lp1 ltp]# ltrace -p 14682

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[04/12 FAILURE] LTPX sysctl03 test fails

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]

Subject: LTP�� sysctl03 test fails

Issues Description Below:
=====================================
# ./runltp -s sysctl03
<<<test_output>>>
sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
sysctl03    2  TFAIL  :  Expected EPERM, got 13
sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails

[Garrett Cooper]

On May 5, 2010, at 11:56 PM, Subrata Modak wrote:

> Subject: LTPś sysctl03 test fails
> 
> Issues Description Below:
> =====================================
> # ./runltp -s sysctl03
> <<<test_output>>>
> sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
> sysctl03    2  TFAIL  :  Expected EPERM, got 13
> sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=1 corefile=no
> cutime=0 cstime=0
> <<<test_end>>>

	Already known and recently discussed.
Thanks,
-Garrett
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails

[Serge E. Hallyn]

Quoting Garrett Cooper (yanegomi@gmail.com):
> On May 5, 2010, at 11:56 PM, Subrata Modak wrote:
> 
> > Subject: LTPś sysctl03 test fails
> > 
> > Issues Description Below:
> > =====================================
> > # ./runltp -s sysctl03
> > <<<test_output>>>
> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
> > sysctl03    2  TFAIL  :  Expected EPERM, got 13
> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
> > <<<execution_status>>>
> > initiation_status="ok"
> > duration=0 termination_type=exited termination_id=1 corefile=no
> > cutime=0 cstime=0
> > <<<test_end>>>
> 
> 	Already known and recently discussed.

Not only can things move glacially in kernel-land, but decisions not
yet implemented can be changed.

In the meantime, the sysctl's sit there as a potential subject for
exploitation.

So not meaning to be argumentative for its own sake, I nevertheless
think it's better to fix the test than either to ignore or remove
it.  Two untested patches below - the one just replaces EPERM with
EACCESS.  The other removes the (imo misuided) notion that we can
guess at the failing errno.  An LSM could choose to return -EPERM
after all, or perhaps even something different.  The thing that
should scare us is if the call succeeds.  If we give any false
positives, then true positives will seem less scary.

-serge

From 2cf7797329275126cc3f80a24bfb8bb2e3f44747 Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <serue@us.ibm.com>
Date: Thu, 6 May 2010 08:30:52 -0500
Subject: [PATCH 1/1] sysctl: check for EACCES

Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
---
 testcases/kernel/syscalls/sysctl/sysctl03.c |   22 +++++++++++-----------
 1 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/testcases/kernel/syscalls/sysctl/sysctl03.c b/testcases/kernel/syscalls/sysctl/sysctl03.c
index f8e743b..e4477f7 100644
--- a/testcases/kernel/syscalls/sysctl/sysctl03.c
+++ b/testcases/kernel/syscalls/sysctl/sysctl03.c
@@ -22,15 +22,15 @@
  *	sysctl03.c
  *
  * DESCRIPTION
- *	Testcase to check that sysctl(2) sets errno to EPERM correctly.
+ *	Testcase to check that sysctl(2) sets errno to EACCES correctly.
  *
  * ALGORITHM
  *	a.	Call sysctl(2) as a root user, and attempt to write data
  *		to the kernel_table[]. Since the table does not have write
- *		permissions even for the root, it should fail EPERM.
+ *		permissions even for the root, it should fail EACCES.
  *	b.	Call sysctl(2) as a non-root user, and attempt to write data
  *		to the kernel_table[]. Since the table does not have write
- *		permission for the regular user, it should fail with EPERM.
+ *		permission for the regular user, it should fail with EACCES.
  *
  * USAGE:  <for command-line>
  *  sysctl03 [-c n] [-e] [-i n] [-I x] [-P x] [-t]
@@ -76,7 +76,7 @@ int sysctl(int *name, int nlen, void *oldval, size_t * oldlenp,
 void setup(void);
 void cleanup(void);
 
-int exp_enos[] = { EPERM, 0 };
+int exp_enos[] = { EACCES, 0 };
 
 int main(int ac, char **av)
 {
@@ -114,13 +114,13 @@ int main(int ac, char **av)
 		} else {
 			TEST_ERROR_LOG(TEST_ERRNO);
 
-			if (TEST_ERRNO != EPERM) {
+			if (TEST_ERRNO != EACCES) {
 				tst_resm(TFAIL,
-					 "Expected EPERM (%d), got %d: %s",
-					 EPERM, TEST_ERRNO,
+					 "Expected EACCES (%d), got %d: %s",
+					 EACCES, TEST_ERRNO,
 					 strerror(TEST_ERRNO));
 			} else {
-				tst_resm(TPASS, "Got expected EPERM error");
+				tst_resm(TPASS, "Got expected EACCES error");
 			}
 		}
 
@@ -147,11 +147,11 @@ int main(int ac, char **av)
 			} else {
 				TEST_ERROR_LOG(TEST_ERRNO);
 
-				if (TEST_ERRNO != EPERM) {
-					tst_resm(TFAIL, "Expected EPERM, got "
+				if (TEST_ERRNO != EACCES) {
+					tst_resm(TFAIL, "Expected EACCES, got "
 						 "%d", TEST_ERRNO);
 				} else {
-					tst_resm(TPASS, "Got expected EPERM "
+					tst_resm(TPASS, "Got expected EACCES "
 						 "error");
 				}
 			}
-- 
1.6.3.3

From c290aeda205afc764f25515b0eaaf9ae05fe3365 Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <serue@us.ibm.com>
Date: Thu, 6 May 2010 08:51:00 -0500
Subject: [PATCH 1/1] accept any sysctl failure

Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
---
 testcases/kernel/syscalls/sysctl/sysctl03.c |   28 +++++---------------------
 1 files changed, 6 insertions(+), 22 deletions(-)

diff --git a/testcases/kernel/syscalls/sysctl/sysctl03.c b/testcases/kernel/syscalls/sysctl/sysctl03.c
index f8e743b..fcd8635 100644
--- a/testcases/kernel/syscalls/sysctl/sysctl03.c
+++ b/testcases/kernel/syscalls/sysctl/sysctl03.c
@@ -22,15 +22,15 @@
  *	sysctl03.c
  *
  * DESCRIPTION
- *	Testcase to check that sysctl(2) sets errno to EPERM correctly.
+ *	Testcase to check that sysctl(2) fail correctly.
  *
  * ALGORITHM
  *	a.	Call sysctl(2) as a root user, and attempt to write data
  *		to the kernel_table[]. Since the table does not have write
- *		permissions even for the root, it should fail EPERM.
+ *		permissions even for the root, it should fail.
  *	b.	Call sysctl(2) as a non-root user, and attempt to write data
  *		to the kernel_table[]. Since the table does not have write
- *		permission for the regular user, it should fail with EPERM.
+ *		permission for the regular user, it should fail.
  *
  * USAGE:  <for command-line>
  *  sysctl03 [-c n] [-e] [-i n] [-I x] [-P x] [-t]
@@ -76,7 +76,7 @@ int sysctl(int *name, int nlen, void *oldval, size_t * oldlenp,
 void setup(void);
 void cleanup(void);
 
-int exp_enos[] = { EPERM, 0 };
+int exp_enos[] = { EPERM, EACCES, 0 };
 
 int main(int ac, char **av)
 {
@@ -113,15 +113,7 @@ int main(int ac, char **av)
 			tst_resm(TFAIL, "sysctl(2) succeeded unexpectedly");
 		} else {
 			TEST_ERROR_LOG(TEST_ERRNO);
-
-			if (TEST_ERRNO != EPERM) {
-				tst_resm(TFAIL,
-					 "Expected EPERM (%d), got %d: %s",
-					 EPERM, TEST_ERRNO,
-					 strerror(TEST_ERRNO));
-			} else {
-				tst_resm(TPASS, "Got expected EPERM error");
-			}
+			tst_resm(TPASS, "sysctl(2) failed as expected.");
 		}
 
 		osnamelth = SIZE(osname);
@@ -145,15 +137,7 @@ int main(int ac, char **av)
 			if (TEST_RETURN != -1) {
 				tst_resm(TFAIL, "call succeeded unexpectedly");
 			} else {
-				TEST_ERROR_LOG(TEST_ERRNO);
-
-				if (TEST_ERRNO != EPERM) {
-					tst_resm(TFAIL, "Expected EPERM, got "
-						 "%d", TEST_ERRNO);
-				} else {
-					tst_resm(TPASS, "Got expected EPERM "
-						 "error");
-				}
+				tst_resm(TPASS, "sysctl failed as expected");
 			}
 
 			cleanup();
-- 
1.6.3.3


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails

[Garrett Cooper]

On Thu, May 6, 2010 at 6:53 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> Quoting Garrett Cooper (yanegomi@gmail.com):
>> On May 5, 2010, at 11:56 PM, Subrata Modak wrote:
>>
>> > Subject: LTPś sysctl03 test fails
>> >
>> > Issues Description Below:
>> > =====================================
>> > # ./runltp -s sysctl03
>> > <<<test_output>>>
>> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
>> > sysctl03    2  TFAIL  :  Expected EPERM, got 13
>> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
>> > <<<execution_status>>>
>> > initiation_status="ok"
>> > duration=0 termination_type=exited termination_id=1 corefile=no
>> > cutime=0 cstime=0
>> > <<<test_end>>>
>>
>>       Already known and recently discussed.
>
> Not only can things move glacially in kernel-land, but decisions not
> yet implemented can be changed.
>
> In the meantime, the sysctl's sit there as a potential subject for
> exploitation.
>
> So not meaning to be argumentative for its own sake, I nevertheless
> think it's better to fix the test than either to ignore or remove
> it.  Two untested patches below - the one just replaces EPERM with
> EACCESS.  The other removes the (imo misuided) notion that we can
> guess at the failing errno.

Except that the documentation (manpages) should explicitly state what
the failing conditions are for any given libcall and syscall. If not,
the Linux kernel devs and documentation team have failed to do their
job.

> An LSM could choose to return -EPERM
> after all, or perhaps even something different.  The thing that
> should scare us is if the call succeeds.  If we give any false
> positives, then true positives will seem less scary.

This will fail on older kernels as sysctl(2) always returned EPERM due
to the way it was improperly designed. Please see the previous thread
for more info: http://lkml.org/lkml/2010/3/4/354

Thanks,
-Garrett

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails

[Serge E. Hallyn]

Quoting Garrett Cooper (yanegomi@gmail.com):
> On Thu, May 6, 2010 at 6:53 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> > Quoting Garrett Cooper (yanegomi@gmail.com):
> >> On May 5, 2010, at 11:56 PM, Subrata Modak wrote:
> >>
> >> > Subject: LTPś sysctl03 test fails
> >> >
> >> > Issues Description Below:
> >> > =====================================
> >> > # ./runltp -s sysctl03
> >> > <<<test_output>>>
> >> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
> >> > sysctl03    2  TFAIL  :  Expected EPERM, got 13
> >> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
> >> > <<<execution_status>>>
> >> > initiation_status="ok"
> >> > duration=0 termination_type=exited termination_id=1 corefile=no
> >> > cutime=0 cstime=0
> >> > <<<test_end>>>
> >>
> >>       Already known and recently discussed.
> >
> > Not only can things move glacially in kernel-land, but decisions not
> > yet implemented can be changed.
> >
> > In the meantime, the sysctl's sit there as a potential subject for
> > exploitation.
> >
> > So not meaning to be argumentative for its own sake, I nevertheless
> > think it's better to fix the test than either to ignore or remove
> > it.  Two untested patches below - the one just replaces EPERM with
> > EACCESS.  The other removes the (imo misuided) notion that we can
> > guess at the failing errno.
> 
> Except that the documentation (manpages) should explicitly state what
> the failing conditions are for any given libcall and syscall. If not,
> the Linux kernel devs and documentation team have failed to do their
> job.

So since we're all member of the doc team, send a patch for sysctl(2)
manpage ERRORS section :)

(mtk cc:d as this is probably news to him)

> > An LSM could choose to return -EPERM
> > after all, or perhaps even something different.  The thing that
> > should scare us is if the call succeeds.  If we give any false
> > positives, then true positives will seem less scary.
> 
> This will fail on older kernels as sysctl(2) always returned EPERM due

Sorry - what will fail?

I think you're saying the first patch will, and I agree, which is why
I advocate the second one i pasted in.

> to the way it was improperly designed. Please see the previous thread
> for more info: http://lkml.org/lkml/2010/3/4/354
> 
> Thanks,
> -Garrett

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails

[Garrett Cooper]

On Thu, May 6, 2010 at 10:55 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> Quoting Garrett Cooper (yanegomi@gmail.com):
>> On Thu, May 6, 2010 at 6:53 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
>> > Quoting Garrett Cooper (yanegomi@gmail.com):
>> >> On May 5, 2010, at 11:56 PM, Subrata Modak wrote:
>> >>
>> >> > Subject: LTPś sysctl03 test fails
>> >> >
>> >> > Issues Description Below:
>> >> > =====================================
>> >> > # ./runltp -s sysctl03
>> >> > <<<test_output>>>
>> >> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
>> >> > sysctl03    2  TFAIL  :  Expected EPERM, got 13
>> >> > sysctl03    1  TFAIL  :  Expected EPERM (1), got 13: Permission denied
>> >> > <<<execution_status>>>
>> >> > initiation_status="ok"
>> >> > duration=0 termination_type=exited termination_id=1 corefile=no
>> >> > cutime=0 cstime=0
>> >> > <<<test_end>>>
>> >>
>> >>       Already known and recently discussed.
>> >
>> > Not only can things move glacially in kernel-land, but decisions not
>> > yet implemented can be changed.
>> >
>> > In the meantime, the sysctl's sit there as a potential subject for
>> > exploitation.
>> >
>> > So not meaning to be argumentative for its own sake, I nevertheless
>> > think it's better to fix the test than either to ignore or remove
>> > it.  Two untested patches below - the one just replaces EPERM with
>> > EACCESS.  The other removes the (imo misuided) notion that we can
>> > guess at the failing errno.
>>
>> Except that the documentation (manpages) should explicitly state what
>> the failing conditions are for any given libcall and syscall. If not,
>> the Linux kernel devs and documentation team have failed to do their
>> job.
>
> So since we're all member of the doc team, send a patch for sysctl(2)
> manpage ERRORS section :)
>
> (mtk cc:d as this is probably news to him)

I already have a bug outstanding for it:
https://bugzilla.kernel.org/show_bug.cgi?id=15446

>> > An LSM could choose to return -EPERM
>> > after all, or perhaps even something different.  The thing that
>> > should scare us is if the call succeeds.  If we give any false
>> > positives, then true positives will seem less scary.
>>
>> This will fail on older kernels as sysctl(2) always returned EPERM due
>
> Sorry - what will fail?

Read through the link, and you will understand why your new proposed
patch with fail with a false negative.

> I think you're saying the first patch will, and I agree, which is why
> I advocate the second one i pasted in.
>
>> to the way it was improperly designed. Please see the previous thread
>> for more info: http://lkml.org/lkml/2010/3/4/354

Thanks,
-Garrett

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails

[Serge E. Hallyn]

Quoting Garrett Cooper (yanegomi@gmail.com):
> On Thu, May 6, 2010 at 10:55 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> > Quoting Garrett Cooper (yanegomi@gmail.com):
> > So since we're all member of the doc team, send a patch for sysctl(2)
> > manpage ERRORS section :)
> >
> > (mtk cc:d as this is probably news to him)
> 
> I already have a bug outstanding for it:
> https://bugzilla.kernel.org/show_bug.cgi?id=15446

That's not what I said :)

> >> > An LSM could choose to return -EPERM
> >> > after all, or perhaps even something different.  The thing that
> >> > should scare us is if the call succeeds.  If we give any false
> >> > positives, then true positives will seem less scary.
> >>
> >> This will fail on older kernels as sysctl(2) always returned EPERM due
> >
> > Sorry - what will fail?
> 
> Read through the link, and you will understand why your new proposed
> patch with fail with a false negative.

I'm not sure that thread means what you think it does.

But look, just trying to help.  And no time for it really.  I'll drop
this.

-serge

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails

[Subrata Modak]

Hmm, so, where do we need to fix this :-(

--Subrata

On Thu, 2010-05-06 at 13:39 -0500, Serge E. Hallyn wrote:
> Quoting Garrett Cooper (yanegomi@gmail.com):
> > On Thu, May 6, 2010 at 10:55 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> > > Quoting Garrett Cooper (yanegomi@gmail.com):
> > > So since we're all member of the doc team, send a patch for sysctl(2)
> > > manpage ERRORS section :)
> > >
> > > (mtk cc:d as this is probably news to him)
> > 
> > I already have a bug outstanding for it:
> > https://bugzilla.kernel.org/show_bug.cgi?id=15446
> 
> That's not what I said :)
> 
> > >> > An LSM could choose to return -EPERM
> > >> > after all, or perhaps even something different.  The thing that
> > >> > should scare us is if the call succeeds.  If we give any false
> > >> > positives, then true positives will seem less scary.
> > >>
> > >> This will fail on older kernels as sysctl(2) always returned EPERM due
> > >
> > > Sorry - what will fail?
> > 
> > Read through the link, and you will understand why your new proposed
> > patch with fail with a false negative.
> 
> I'm not sure that thread means what you think it does.
> 
> But look, just trying to help.  And no time for it really.  I'll drop
> this.
> 
> -serge


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

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [04/12 FAILURE] LTP? sysctl03 test fails

[Garrett Cooper]

On Thu, May 6, 2010 at 11:39 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> Quoting Garrett Cooper (yanegomi@gmail.com):
>> On Thu, May 6, 2010 at 10:55 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
>> > Quoting Garrett Cooper (yanegomi@gmail.com):
>> > So since we're all member of the doc team, send a patch for sysctl(2)
>> > manpage ERRORS section :)
>> >
>> > (mtk cc:d as this is probably news to him)
>>
>> I already have a bug outstanding for it:
>> https://bugzilla.kernel.org/show_bug.cgi?id=15446
>
> That's not what I said :)

    Yeah, I understand. If you guys agree with the content, I will
submit a patch. Otherwise, the item will unfortunately remain dead in
the water :(.

>> >> > An LSM could choose to return -EPERM
>> >> > after all, or perhaps even something different.  The thing that
>> >> > should scare us is if the call succeeds.  If we give any false
>> >> > positives, then true positives will seem less scary.
>> >>
>> >> This will fail on older kernels as sysctl(2) always returned EPERM due
>> >
>> > Sorry - what will fail?
>>
>> Read through the link, and you will understand why your new proposed
>> patch with fail with a false negative.
>
> I'm not sure that thread means what you think it does.

   Yes, I think it does mean what I think it does. 2.6.32 was
`corrected' to do a lot more things, one of which was to return EPERM
in certain cases where it completely bypassed that return code before.
That's why you're seeing the error now whereas before it was
completely bypassed :/.

> But look, just trying to help.  And no time for it really.  I'll drop
> this.

    I appreciate your help as do a lot of other folks. I'm just trying
to (in my own pedantic way) be as unflexible as possible because the
requirements for each function call as per the documentation should be
crystal clear, as should the testcases. If not, then the developers
that develop against those requirements won't know what to expect and
bugs will only be introduced by accident into software. I don't want
that to happen and that's why I am the way I am.
Thanks,
-Garrett

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

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[05/12 FAILURE] LTPX proc01 test fails

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

Subject: LTP�� proc01 test fail

Issues Description below:
====================================
# ./runltp -s proc01

<<<test_output>>>
proc01      0  TINFO  :  /proc/sysrq-trigger: is write-only.
proc01      0  TINFO  :  /proc/kmsg: known issue: errno=EAGAIN(11): Resource
temporarily unavailable
proc01      0  TINFO  :  /proc/powerpc/ofdt: is write-only.
proc01      1  TFAIL  :  read failed: /proc/powerpc/rtas/error_log:
errno=EINVAL(22): Invalid argument
proc01      0  TINFO  :  /proc/sys/fs/binfmt_misc/register: is write-only.
proc01      0  TINFO  :  /proc/self/task/7928/mem: known issue: errno=EIO(5):
Input/output error
proc01      0  TINFO  :  /proc/self/task/7928/clear_refs: is write-only.
proc01      0  TINFO  :  /proc/self/mem: known issue: errno=EIO(5):
Input/output error
proc01      0  TINFO  :  /proc/self/clear_refs: is write-only.
proc01      2  TFAIL  :  readproc() failed with 1 errors.
<<<execution_status>>>
initiation_status="ok"
duration=2 termination_type=exited termination_id=1 corefile=no
cutime=4 cstime=130
<<<test_end>>>

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [05/12 FAILURE] LTP? proc01 test fails

[Garrett Cooper]

On May 5, 2010, at 11:57 PM, Subrata Modak wrote:

> Subject: LTPś proc01 test fail
> 
> Issues Description below:
> ====================================
> # ./runltp -s proc01
> 
> <<<test_output>>>
> proc01      0  TINFO  :  /proc/sysrq-trigger: is write-only.
> proc01      0  TINFO  :  /proc/kmsg: known issue: errno=EAGAIN(11): Resource
> temporarily unavailable
> proc01      0  TINFO  :  /proc/powerpc/ofdt: is write-only.
> proc01      1  TFAIL  :  read failed: /proc/powerpc/rtas/error_log:
> errno=EINVAL(22): Invalid argument

	Not a known issue. I'd check and see whether or not this item is valid. Seems like a funky error code though.
HTH,
-Garrett
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [05/12 FAILURE] LTP? proc01 test fails

[Subrata Modak]

This is fixed now in the latest LTP.

Regards--
Subrata

On Thu, 2010-05-06 at 01:04 -0700, Garrett Cooper wrote:
> On May 5, 2010, at 11:57 PM, Subrata Modak wrote:
> 
> > Subject: LTPś proc01 test fail
> > 
> > Issues Description below:
> > ====================================
> > # ./runltp -s proc01
> > 
> > <<<test_output>>>
> > proc01      0  TINFO  :  /proc/sysrq-trigger: is write-only.
> > proc01      0  TINFO  :  /proc/kmsg: known issue: errno=EAGAIN(11): Resource
> > temporarily unavailable
> > proc01      0  TINFO  :  /proc/powerpc/ofdt: is write-only.
> > proc01      1  TFAIL  :  read failed: /proc/powerpc/rtas/error_log:
> > errno=EINVAL(22): Invalid argument
> 
> 	Not a known issue. I'd check and see whether or not this item is valid. Seems like a funky error code though.
> HTH,
> -Garrett


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [05/12 FAILURE] LTP? proc01 test fails

[Subrata Modak]

This is fixed now in latest LTP.

Regards--
Subrata

On Thu, 2010-05-06 at 01:04 -0700, Garrett Cooper wrote:
> On May 5, 2010, at 11:57 PM, Subrata Modak wrote:
> 
> > Subject: LTPś proc01 test fail
> > 
> > Issues Description below:
> > ====================================
> > # ./runltp -s proc01
> > 
> > <<<test_output>>>
> > proc01      0  TINFO  :  /proc/sysrq-trigger: is write-only.
> > proc01      0  TINFO  :  /proc/kmsg: known issue: errno=EAGAIN(11): Resource
> > temporarily unavailable
> > proc01      0  TINFO  :  /proc/powerpc/ofdt: is write-only.
> > proc01      1  TFAIL  :  read failed: /proc/powerpc/rtas/error_log:
> > errno=EINVAL(22): Invalid argument
> 
> 	Not a known issue. I'd check and see whether or not this item is valid. Seems like a funky error code though.
> HTH,
> -Garrett


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[LTP] [06/12 FAILURE] Many CONTAINER tests of LTP fail

[Subrata Modak]

Subject:Many CONTAINER tests of LTP fail

I know Serge and Dan is already working on it.

Issues Description Below:
====================================================
# ./runltp -f containers
<<<test_start>>>
tag=Containers stime=1271856718
cmdline="container_test.sh"
contacts=""
analysis=exit
<<<test_output>>>
Running utsns tests.
unshare tests
test 1 (unshare)
uts_namespace    1  TPASS  :  test 1 (unshare): success
test 2 (unshare)
uts_namespace    1  TPASS  :  test 2 (unshare): success
test 3 (unshare)
uts_namespace    1  TPASS  :  test 3 (unshare): success
test 4 (unshare)
uts_namespace    1  TPASS  :  test 4 (unshare): successful
test 5 (unshare)
uts_namespace    1  TPASS  :  P2: P1 claims error
clone tests
test 1 (clone)
uts_namespace    1  TPASS  :  test 1 (clone): success
test 2 (clone)
uts_namespace    1  TPASS  :  test 2 (clone): success
test 3 (clone)
uts_namespace    1  TPASS  :  test 3 (clone): success
test 4 (clone)
uts_namespace    1  TPASS  :  test 4 (clone): successful
test 5 (clone)
uts_namespace    1  TPASS  :  P2: P1 claims error
Running ipcns tests.
****************** sysvipc tests ******************
sysvipc: SharedMemory none
sysvipc_namespace    0  TINFO  :  shmid namespaces test : none
sysvipc_namespace    1  TPASS  :  plain cloned process found shmid
sysvipc_namespace    0  TINFO  :  shmid namespaces test : none
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : none
shmem_2nstest    0  TINFO  :  Cont1: Able to create shared mem segment
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : none
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : none
shmem_2nstest    1  TPASS  :  Plain cloned process able to access shmem segment
created
sysvipc: SharedMemory clone
sysvipc_namespace    0  TINFO  :  shmid namespaces test : clone
sysvipc_namespace    0  TINFO  :  shmid namespaces test : clone
sysvipc_namespace    1  TPASS  :  clone: child process didn't find shmid
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : clone
shmem_2nstest    0  TINFO  :  Cont1: Able to create shared mem segment
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : clone
shmem_2nstest    0  TINFO  :  Cont2: Able to allocate shmem seg with the same
key
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : clone
shmem_2nstest    1  TPASS  :  clone : In namespace2 unable to access the shmem
seg created in Namespace1
sysvipc: SharedMemory unshare
sysvipc_namespace    0  TINFO  :  shmid namespaces test : unshare
sysvipc_namespace    0  TINFO  :  shmid namespaces test : unshare
sysvipc_namespace    1  TPASS  :  unshare: child process didn't find shmid
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : unshare
shmem_2nstest    0  TINFO  :  Cont1: Able to create shared mem segment
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : unshare
shmem_2nstest    0  TINFO  :  Cont2: Able to allocate shmem seg with the same
key
shmem_2nstest    0  TINFO  :  Shared Memory namespace test : unshare
shmem_2nstest    1  TPASS  :  unshare : In namespace2 unable to access the
shmem seg created in Namespace1
sysvipc: MesgQ none
mesgq_nstest    0  TINFO  :  mesgq namespaces test : none
mesgq_nstest    1  TPASS  :  Plain cloned process found mesgq inside container
mesgq_nstest    0  TINFO  :  mesgq namespaces test : none
mesgq_nstest    0  TINFO  :  Mesg read of 18 bytes; Type 5: Msg: Message of
type 5!
sysvipc: MesgQ clone
mesgq_nstest    0  TINFO  :  mesgq namespaces test : clone
mesgq_nstest    0  TINFO  :  mesgq namespaces test : clone
mesgq_nstest    1  TPASS  :  clone: Container didn't find mesgq
sysvipc: MesgQ unshare
mesgq_nstest    0  TINFO  :  mesgq namespaces test : unshare
mesgq_nstest    0  TINFO  :  mesgq namespaces test : unshare
mesgq_nstest    1  TPASS  :  unshare: Container didn't find mesgq
sysvipc: Semaphore none
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : none
sem_nstest    1  TPASS  :  Plain cloned process found semaphore inside
container
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : none
sem_nstest    0  TINFO  :  PID 4362: Fetched existing semaphore..id = 10158080
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : none
semtest_2ns    0  TINFO  :  Cont1: Able to create semaphore
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : none
semtest_2ns    0  TINFO  :  Sem1: File locked, Critical section is updated...
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : none
semtest_2ns    1  TPASS  :  Plain cloned process able to access the semaphore
created
sysvipc: Semaphore clone
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : clone
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : clone
sem_nstest    1  TPASS  :  clone: Container didn't find semaphore
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : clone
semtest_2ns    0  TINFO  :  Cont1: Able to create semaphore
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : clone
semtest_2ns    0  TINFO  :  Cont2: Able to create semaphore with sameKey
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : clone
semtest_2ns    1  TPASS  :  clone : In namespace2 unable to access the
semaphore created in Namespace1
sysvipc: Semaphore unshare
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : unshare
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : unshare
sem_nstest    1  TPASS  :  unshare: Container didn't find semaphore
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : unshare
semtest_2ns    0  TINFO  :  Cont1: Able to create semaphore
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : unshare
semtest_2ns    0  TINFO  :  Cont2: Able to create semaphore with sameKey
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : unshare
semtest_2ns    1  TPASS  :  unshare : In namespace2 unable to access the
semaphore created in Namespace1
Running pidns tests.
pid_namespace1    0  TINFO  :  PIDNS test is running inside container
pid_namespace1    1  TPASS  :  Success:
pid_namespace3    0  TINFO  :   Checking pid for parent ns and container-init
                                Parent namespace pid = 4383,container parent
pid = 0,and container pid = 1
pid_namespace3    1  TFAIL  :  Failed to open /proc directory
pid_namespace4    0  TINFO  :  PIDNS test is running inside container
pid_namespace4    1  TPASS  :  Container init : I was not killed !
pidns05     0  TINFO  :   5 Nested Containers are created
pidns05     1  TPASS  :  The number of containers killed are 2
pidns06     0  TINFO  :  Parent: Passing the pid of the process 4394
pidns06     1  TPASS  :  Container: tried kill() on the parent pid 4394: errno
set to 3 (No such process), as expected
pidns06     2  TPASS  :  Container: While killing non existent pid errno set to
3 : No such process, as expected
pidns06     0  TINFO  :  Parent: Passing the pid of the process 4394
pidns30     1  TBROK  :  parent: mq_open() failed (Permission denied)
pidns31     1  TBROK  :  parent: mq_open() failed (Permission denied)
pidns10     1  TPASS  :  cinit: expected kill(-1, sig) failure.
pidns12     0  TINFO  :  parent: PID is 4400
pidns12     1  TPASS  :  cinit: signalling PID (from other namespace) is 0 as
expected
pidns12     0  TINFO  :  parent: PID is 4400
pidns13     0  TINFO  :  cinit2: writing some data in pipe
pidns13     0  TINFO  :  cinit1: setup handler for async I/O on pipe
pidns13     1  TPASS  :  cinit1: si_fd is 5, si_code is 1
pidns16     1  TPASS  :  container init continued successfuly, after handling
signal -USR1
pidns17     1  TPASS  :  cinit: all children are terminated.
pidns20     0  TINFO  :  cinit: blocked SIGUSR1
pidns20     0  TINFO  :  cinit: unblocking SIGUSR1
pidns20     1  TPASS  :  cinit: user function is called as expected
pidns20     0  TINFO  :  parent: signalled SIGUSR1 to container
Running POSIX message queue tests.
mq_open: Permission denied
posixmq_namespace_01    0  TINFO  :  Testing posix mq namespaces through
unshare(2).
posixmq_namespace_01    1  TFAIL  :  mq_open failed
Running netns tests.
parentns.sh    0  TINFO  :  PASS: Pinging ChildNS from ParentNS
sshd re-exec requires execution with an absolute path^M
childns.sh    0  TINFO  :  PASS: Pinging ParentNS from ChildNS
crtchild: PASS
netns_2children    1  TFAIL  :  Error while running the scripts
two_children_ns: return code is 1 ;
sshd re-exec requires execution with an absolute path^M
childns.sh    0  TINFO  :  Successfully Renamed device to veth1
Files /tmp/sys_b4_child_killed and /tmp/sys_aftr_child_killed differ
Cannot find device "veth1"
crtchild_delchild: PASS
paripv6.sh    0  TINFO  :  IPv6: Pinging child from parent: PASS
childipv6.sh    0  TINFO  :  IPv6: Pinging Parent from Child: PASS
par_chld_ipv6: PASS
parentns.sh    0  TINFO  :  Pinging ChildNS from ParentNS
sshd re-exec requires execution with an absolute path^M
Error: Can't ftp to 192.168.0.181: Connection refused
childns.sh    1  TFAIL  :  ftp failed
Error while running the script
two_children_ns: return code is 1 ; par_chld_ftp: FAIL 1 ;
<<<execution_status>>>
initiation_status="ok"
duration=41 termination_type=exited termination_id=1 corefile=no
cutime=14 cstime=98
<<<test_end>>>

Regards--
Subrata


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [06/12 FAILURE] Many CONTAINER tests of LTP fail

[Garrett Cooper]

Clipping the output to denote the failures.

On Wed, May 5, 2010 at 11:57 PM, Subrata Modak
<subrata@linux.vnet.ibm.com> wrote:
> Subject:Many CONTAINER tests of LTP fail
>
> I know Serge and Dan is already working on it.
>
> Issues Description Below:
> ====================================================
> # ./runltp -f containers
> <<<test_start>>>

[...]

> pid_namespace3    1  TFAIL  :  Failed to open /proc directory

This is interesting... is /proc not mounted in the child container?

> pidns30     1  TBROK  :  parent: mq_open() failed (Permission denied)
> pidns31     1  TBROK  :  parent: mq_open() failed (Permission denied)

Does the queue exist?

> posixmq_namespace_01    1  TFAIL  :  mq_open failed
> Running netns tests.

[...]

> netns_2children    1  TFAIL  :  Error while running the scripts
> two_children_ns: return code is 1 ;
> sshd re-exec requires execution with an absolute path^M

This was going to be fixed with a patch proposed earlier.

> childns.sh    0  TINFO  :  Successfully Renamed device to veth1
> Files /tmp/sys_b4_child_killed and /tmp/sys_aftr_child_killed differ
> Cannot find device "veth1"
> crtchild_delchild: PASS

This seems suspect even though it says passed.

[...]

> sshd re-exec requires execution with an absolute path^M
> Error: Can't ftp to 192.168.0.181: Connection refused
> childns.sh    1  TFAIL  :  ftp failed

One of the prereqs is missing probably (setup an ftp daemon ... maybe
this was going to be done via ssh?)

[...]

> <<<test_end>>>

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [06/12 FAILURE] Many CONTAINER tests of LTP fail

[Dan Smith]

>> childns.sh    0  TINFO  :  Successfully Renamed device to veth1
>> Files /tmp/sys_b4_child_killed and /tmp/sys_aftr_child_killed differ
>> Cannot find device "veth1"
>> crtchild_delchild: PASS

GC> This seems suspect even though it says passed.

The logic is inverted which causes it to continue only if the sshd
exec fails.  Fixed in my patch as well.

GC> One of the prereqs is missing probably (setup an ftp daemon
GC> ... maybe this was going to be done via ssh?)

It looks to me like the test requires a (rather loosely-configured)
ftp daemon running in the init netns for this to pass.

-- 
Dan Smith
IBM Linux Technology Center
email: danms@us.ibm.com

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [06/12 FAILURE] Many CONTAINER tests of LTP fail

[Subrata Modak]

Hi Suka,

Some issues continue to exist in latest LTP. Do you have proposal for
them:

<<<test_start>>>
tag=Containers stime=1280251869
cmdline="container_test.sh"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
Running utsns tests.
unshare tests
test 1 (unshare)
uts_namespace    1  TPASS  :  test 1 (unshare): success

test 2 (unshare)
uts_namespace    1  TPASS  :  test 2 (unshare): success

test 3 (unshare)
uts_namespace    1  TPASS  :  test 3 (unshare): success

test 4 (unshare)
uts_namespace    1  TPASS  :  test 4 (unshare): successful

test 5 (unshare)
uts_namespace    1  TPASS  :  P2: P1 claims error

clone tests
test 1 (clone)
uts_namespace    1  TPASS  :  test 1 (clone): success

test 2 (clone)
uts_namespace    1  TPASS  :  test 2 (clone): success

test 3 (clone)
uts_namespace    1  TPASS  :  test 3 (clone): success

test 4 (clone)
uts_namespace    1  TPASS  :  test 4 (clone): successful

test 5 (clone)
uts_namespace    1  TPASS  :  P2: P1 claims error

Running ipcns tests.
****************** sysvipc tests ******************
sysvipc: SharedMemory none
sysvipc_namespace    0  TINFO  :  shmid namespaces test : none

sysvipc_namespace    1  TPASS  :  plain cloned process found shmid

shmem_2nstest    0  TINFO  :  Shared Memory namespace test : none
shmem_2nstest    0  TINFO  :  Cont1: Able to create shared mem segment
shmem_2nstest    1  TPASS  :  Plain cloned process able to access shmem
segment created

sysvipc: SharedMemory clone
sysvipc_namespace    0  TINFO  :  shmid namespaces test : clone

sysvipc_namespace    1  TPASS  :  clone: child process didn't find shmid

shmem_2nstest    0  TINFO  :  Shared Memory namespace test : clone
shmem_2nstest    0  TINFO  :  Cont1: Able to create shared mem segment
shmem_2nstest    0  TINFO  :  Cont2: Able to allocate shmem seg with the
same key
shmem_2nstest    1  TPASS  :  clone : In namespace2 unable to access the
shmem seg created in Namespace1

sysvipc: SharedMemory unshare
sysvipc_namespace    0  TINFO  :  shmid namespaces test : unshare

sysvipc_namespace    1  TPASS  :  unshare: child process didn't find
shmid

shmem_2nstest    0  TINFO  :  Shared Memory namespace test : unshare
shmem_2nstest    0  TINFO  :  Cont1: Able to create shared mem segment
shmem_2nstest    0  TINFO  :  Cont2: Able to allocate shmem seg with the
same key
shmem_2nstest    1  TPASS  :  unshare : In namespace2 unable to access
the shmem seg created in Namespace1


sysvipc: MesgQ none
mesgq_nstest    0  TINFO  :  mesgq namespaces test : none

mesgq_nstest    1  TPASS  :  Plain cloned process found mesgq inside
container

mesgq_nstest    0  TINFO  :  Mesg read of 18 bytes; Type 5: Msg: Message
of type 5!

sysvipc: MesgQ clone
mesgq_nstest    0  TINFO  :  mesgq namespaces test : clone

mesgq_nstest    1  TPASS  :  clone: Container didn't find mesgq
sysvipc: MesgQ unshare
mesgq_nstest    0  TINFO  :  mesgq namespaces test : unshare

mesgq_nstest    1  TPASS  :  unshare: Container didn't find mesgq

sysvipc: Semaphore none
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : none

sem_nstest    1  TPASS  :  Plain cloned process found semaphore inside
container

sem_nstest    0  TINFO  :  PID 25710: Fetched existing semaphore..id = 0

semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : none
semtest_2ns    0  TINFO  :  Cont1: Able to create semaphore
semtest_2ns    0  TINFO  :  Sem1: File locked, Critical section is
updated...

semtest_2ns    1  TPASS  :  Plain cloned process able to access the
semaphore created

sysvipc: Semaphore clone
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : clone

sem_nstest    1  TPASS  :  clone: Container didn't find semaphore
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : clone
semtest_2ns    0  TINFO  :  Cont1: Able to create semaphore
semtest_2ns    0  TINFO  :  Cont2: Able to create semaphore with sameKey
semtest_2ns    1  TPASS  :  clone : In namespace2 unable to access the
semaphore created in Namespace1

sysvipc: Semaphore unshare
sem_nstest    0  TINFO  :  Semaphore namespaces Isolation test : unshare

sem_nstest    1  TPASS  :  unshare: Container didn't find semaphore
semtest_2ns    0  TINFO  :  Semaphore Namespaces Test : unshare
semtest_2ns    0  TINFO  :  Cont1: Able to create semaphore
semtest_2ns    0  TINFO  :  Cont2: Able to create semaphore with sameKey
semtest_2ns    1  TPASS  :  unshare : In namespace2 unable to access the
semaphore created in Namespace1


Running pidns tests.
pid_namespace1    0  TINFO  :  PIDNS test is running inside container

pid_namespace1    1  TPASS  :  Success:
pid_namespace2    0  TINFO  :  Checking session id & group id inside
container

pid_namespace2    1  TPASS  :  Success: Got Group ID = 1 & Session ID =
1 

pid_namespace3    0  TINFO  :   Checking pid for parent ns and
container-init
                                Parent namespace pid = 25731,container
parent pid = 0,and container pid = 1
pid_namespace3    1  TFAIL  :  Failed to open /proc directory
pid_namespace4    0  TINFO  :  PIDNS test is running inside container
pid_namespace4    1  TPASS  :  Container init : I was not killed !
pidns05     0  TINFO  :   5 Nested Containers are created
pidns05     1  TPASS  :  The number of containers killed are 2

pidns06     0  TINFO  :  Parent: Passing the pid of the process 25742
pidns06     1  TPASS  :  Container: tried kill() on the parent pid
25742: errno set to 3 (No such process), as expected

pidns06     2  TPASS  :  Container: While killing non existent pid errno
set to 3 : No such process, as expected

pidns30     0  TINFO  :  parent: successfully created posix mqueue
pidns30     0  TINFO  :  cinit: mq_open succeeded
pidns30     0  TINFO  :  cinit: successfully registered for notification
pidns30     0  TINFO  :  cinit: successfully registered handler for
SIGUSR1
pidns30     1  TPASS  :  cinit: signal originator PID = 0
pidns30     0  TINFO  :  parent: mq_send() succeeded
pidns30     0  TINFO  :  cinit: my father is done - cleaning
pidns31     1  TBROK  :  parent: mq_open() failed (Permission denied)
pidns10     1  TPASS  :  cinit: expected kill(-1, sig) failure.
pidns12     0  TINFO  :  parent: PID is 25749
pidns12     1  TPASS  :  cinit: signalling PID (from other namespace) is
0 as expected
pidns13     0  TINFO  :  cinit1: setup handler for async I/O on pipe
pidns13     0  TINFO  :  cinit2: writing some data in pipe
pidns13     1  TPASS  :  cinit1: si_fd is 5, si_code is 1
pidns16     1  TBROK  :  Unexpected value for Sending-ProcessID when
signal handler called 0

pidns16     0  TINFO  :  Container: Resumed after receiving SIGUSR1 from
parentNS 
pidns16     0  TINFO  :  sig_handler is signalled from pid  1
pidns16     0  TINFO  :  Container: Resumed after sending SIGUSR1 from
container itself
pidns16     1  TPASS  :  container init continued successfuly, after
handling signal -USR1

pidns17     1  TPASS  :  cinit: all children are terminated.
pidns20     0  TINFO  :  cinit: blocked SIGUSR1
pidns20     0  TINFO  :  parent: signalled SIGUSR1 to container
pidns20     0  TINFO  :  cinit: unblocking SIGUSR1
pidns20     1  TPASS  :  cinit: user function is called as expected
Running POSIX message queue tests.
posixmq_namespace_01    0  TINFO  :  Testing posix mq namespaces through
unshare(2).

posixmq_namespace_01    0  TINFO  :  Checking namespaces isolation from
parent to child

posixmq_namespace_01    1  TPASS  :  child process didn't find mqueue

posixmq_namespace_01    0  TINFO  :  Testing posix mq namespaces through
clone(2).

posixmq_namespace_01    0  TINFO  :  Checking namespaces isolation from
parent to child

posixmq_namespace_01    1  TPASS  :  child process didn't find mqueue

posixmq_namespace_02    0  TINFO  :  Testing posix mq namespaces through
unshare(2).

posixmq_namespace_02    0  TINFO  :  Checking namespaces isolation
(child to parent)

posixmq_namespace_02    1  TPASS  :  Parent process can't see the mqueue

posixmq_namespace_02    0  TINFO  :  Testing posix mq namespaces through
clone(2).

posixmq_namespace_02    0  TINFO  :  Checking namespaces isolation
(child to parent)

posixmq_namespace_02    1  TPASS  :  Parent process can't see the mqueue

posixmq_namespace_03    0  TINFO  :  Testing posix mq namespaces through
unshare(2).

posixmq_namespace_03    0  TINFO  :  Checking correct umount+remount of
mqueuefs

posixmq_namespace_03    1  TPASS  :  umount+remount of mqueuefs
remounted the right fs

posixmq_namespace_03    0  TINFO  :  Testing posix mq namespaces through
clone(2).

posixmq_namespace_03    0  TINFO  :  Checking correct umount+remount of
mqueuefs

posixmq_namespace_03    1  TPASS  :  umount+remount of mqueuefs
remounted the right fs

posixmq_namespace_04    0  TINFO  :  Testing posix mq namespaces through
unshare(2).

posixmq_namespace_04    0  TINFO  :  Checking mqueue filesystem lifetime

posixmq_namespace_04    1  TPASS  :  Child mqueue fs still visible for
parent

posixmq_namespace_04    0  TINFO  :  Testing posix mq namespaces through
clone(2).

posixmq_namespace_04    0  TINFO  :  Checking mqueue filesystem lifetime

posixmq_namespace_04    1  TPASS  :  Child mqueue fs still visible for
parent

Running netns tests.
parentns.sh    0  TINFO  :  PASS: Pinging ChildNS from ParentNS
childns.sh    0  TINFO  :  PASS: Pinging ParentNS from ChildNS
crtchild: PASS

child_2.sh    0  TINFO  :  PASS: CHILD1 is pinging from CHILD2 ! 
child_1.sh    0  TINFO  :  PASS: Child2 is pinging from CHILD1 !
two_children_ns: PASS

childns.sh    0  TINFO  :  Successfully Renamed device to veth2
Files /tmp/sys_b4_child_killed and /tmp/sys_aftr_child_killed differ
Cannot find device "veth0"
crtchild_delchild: PASS

paripv6.sh    0  TINFO  :  IPv6: Pinging child from parent: PASS
childipv6.sh    0  TINFO  :  IPv6: Pinging Parent from Child: PASS
par_chld_ipv6: PASS

parentns.sh    0  TINFO  :  Pinging ChildNS from ParentNS
Error: Can't ftp to 192.168.0.181: Connection refused
childns.sh    1  TFAIL  :  ftp failed
Error while running the script
par_chld_ftp: FAIL 1 ;

<<<execution_status>>>
initiation_status="ok"
duration=47 termination_type=exited termination_id=1 corefile=no
cutime=20 cstime=112
<<<test_end>>>
/opt/ltp/testcases/bin/initialize.sh: line 83:    57 Terminated
( ip link delete $netdev ) 2> /dev/null
INFO: ltp-pan reported some tests FAIL
LTP Version: LTP-20100630
        
       ###############################################################"
        
            Done executing testcases."
            LTP Version:  LTP-20100630
       ###############################################################"

Regards--
Subrata

On Thu, 2010-05-06 at 10:53 -0700, Garrett Cooper wrote:
> Clipping the output to denote the failures.
> 
> On Wed, May 5, 2010 at 11:57 PM, Subrata Modak
> <subrata@linux.vnet.ibm.com> wrote:
> > Subject:Many CONTAINER tests of LTP fail
> >
> > I know Serge and Dan is already working on it.
> >
> > Issues Description Below:
> > ====================================================
> > # ./runltp -f containers
> > <<<test_start>>>
> 
> [...]
> 
> > pid_namespace3    1  TFAIL  :  Failed to open /proc directory
> 
> This is interesting... is /proc not mounted in the child container?
> 
> > pidns30     1  TBROK  :  parent: mq_open() failed (Permission denied)
> > pidns31     1  TBROK  :  parent: mq_open() failed (Permission denied)
> 
> Does the queue exist?
> 
> > posixmq_namespace_01    1  TFAIL  :  mq_open failed
> > Running netns tests.
> 
> [...]
> 
> > netns_2children    1  TFAIL  :  Error while running the scripts
> > two_children_ns: return code is 1 ;
> > sshd re-exec requires execution with an absolute path^M
> 
> This was going to be fixed with a patch proposed earlier.
> 
> > childns.sh    0  TINFO  :  Successfully Renamed device to veth1
> > Files /tmp/sys_b4_child_killed and /tmp/sys_aftr_child_killed differ
> > Cannot find device "veth1"
> > crtchild_delchild: PASS
> 
> This seems suspect even though it says passed.
> 
> [...]
> 
> > sshd re-exec requires execution with an absolute path^M
> > Error: Can't ftp to 192.168.0.181: Connection refused
> > childns.sh    1  TFAIL  :  ftp failed
> 
> One of the prereqs is missing probably (setup an ftp daemon ... maybe
> this was going to be done via ssh?)
> 
> [...]
> 
> > <<<test_end>>>


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[07/12 FAILURE] LTPX MEMORY CGROUP FUNCTION tests fails

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4607 bytes --]

Subject: LTP�� MEMORY CGROUP FUNCTION tests fails

Issues Description Below:
==================================
# vi runtest/memcg_function
memcg_function          memcg_function_test.sh$PAGESIZE $((PAGESIZE * 2))
<EOF>

Run LTP with the following command:
# ./runltp -f memcg_function
<<<test_start>>>
tag=memcg_function stime=1271856934
cmdline="       memcg_function_test.sh"
contacts=""
analysis=exit
<<<test_output>>>
memcg_function_test    1  TPASS  :  rss=4096/4096, cache=0/0
memcg_function_test    2  TPASS  :  rss=0/0, cache=4096/4096
memcg_function_test    3  TPASS  :  rss=0/0, cache=4096/4096
memcg_function_test    4  TPASS  :  rss=4096/4096, cache=8192/8192
memcg_function_test    5  TPASS  :  rss=4096/4096, cache=0/0
memcg_function_test    6  TPASS  :  rss=4096/4096, cache=0/0
memcg_function_test    6  TPASS  :  rss=0/0, cache=0/0
memcg_function_test    7  TPASS  :  rss=0/0, cache=4096/4096
memcg_function_test    7  TPASS  :  rss=0/0, cache=0/0
memcg_function_test    8  TPASS  :  rss=0/0, cache=4096/4096
memcg_function_test    8  TPASS  :  rss=0/0, cache=0/0
memcg_function_test    9  TFAIL  :  rss=8192/4096, cache=8192/8192
memcg_function_test    9  TFAIL  :  rss=4096/0, cache=0/0
memcg_function_test   10  TPASS  :  rss=4096/4096, cache=0/0
memcg_function_test   10  TPASS  :  rss=0/0, cache=0/0
/opt/ltp/testcases/bin/memcg_function_test.sh: line 106: 18335 Killed          
       $TEST_PATH/memcg_process $1 -s $2
memcg_function_test   11  TPASS  :  failcnt=8
/opt/ltp/testcases/bin/memcg_function_test.sh: line 106: 18351 Killed          
       $TEST_PATH/memcg_process $1 -s $2
memcg_function_test   12  TPASS  :  failcnt=8
/opt/ltp/testcases/bin/memcg_function_test.sh: line 106: 18367 Killed          
       $TEST_PATH/memcg_process $1 -s $2
memcg_function_test   13  TPASS  :  failcnt=8
/opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18385 Killed          
       $TEST_PATH/memcg_process $2 -s $3
memcg_function_test   14  TPASS  :  process 18385 is killed
/opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18398 Killed          
       $TEST_PATH/memcg_process $2 -s $3
memcg_function_test   15  TPASS  :  process 18398 is killed
/opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18414 Killed          
       $TEST_PATH/memcg_process $2 -s $3
memcg_function_test   16  TPASS  :  process 18414 is killed
/opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18432 Killed          
       $TEST_PATH/memcg_process $2 -s $3
memcg_function_test   17  TPASS  :  process 18432 is killed
/opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18450 Killed          
       $TEST_PATH/memcg_process $2 -s $3
memcg_function_test   18  TPASS  :  process 18450 is killed
/opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18467 Killed          
       $TEST_PATH/memcg_process $2 -s $3
memcg_function_test   19  TPASS  :  process 18467 is killed
/opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18482 Killed          
       $TEST_PATH/memcg_process $2 -s $3
memcg_function_test   20  TPASS  :  process 18482 is killed
/opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18495 Killed          
       $TEST_PATH/memcg_process $2 -s $3
memcg_function_test   21  TPASS  :  process 18495 is killed
memcg_function_test   22  TPASS  :  input=4095, limit_in_bytes=4096
memcg_function_test   23  TPASS  :  input=4097, limit_in_bytes=8192
memcg_function_test   24  TPASS  :  input=1, limit_in_bytes=4096
memcg_function_test   25  TPASS  :  return value is 0
memcg_function_test   26  TPASS  :  return value is 1
memcg_function_test   27  TPASS  :  return value is 1
memcg_function_test   28  TPASS  :  return value is 1
memcg_function_test   29  TPASS  :  force memory succeeded
memcg_function_test   30  TPASS  :  force memory failed as expected
memcg_function_test   31  TPASS  :  return value is 0
memcg_function_test   32  TPASS  :  return value is 0
memcg_function_test   33  TPASS  :  return value is 0
memcg_function_test   34  TPASS  :  return value is 0
memcg_function_test   35  TPASS  :  return value is 1
memcg_function_test   36  TPASS  :  rss=4096/4096, cache=0/0
memcg_function_test   36  TPASS  :  rss=0/0, cache=0/0
memcg_function_test   37  TPASS  :  rss=4096/4096, cache=0/0
memcg_function_test   37  TPASS  :  rss=0/0, cache=0/0
memcg_function_test   38  TPASS  :  rss=4096/4096, cache=0/0
memcg_function_test   38  TPASS  :  rss=0/0, cache=0/0
<<<execution_status>>>
initiation_status="ok"
duration=110 termination_type=exited termination_id=1 corefile=no
cutime=15 cstime=282
<<<test_end>>>

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [07/12 FAILURE] LTPE MEMORY CGROUP FUNCTION tests fails

[Subrata Modak]

This is no more reproducible.

Regards--
Subrata

On Thu, 2010-05-06 at 12:27 +0530, Subrata Modak wrote:
> Subject: LTPE^[ MEMORY CGROUP FUNCTION tests fails
> 
> Issues Description Below:
> ==================================
> # vi runtest/memcg_function
> memcg_function          memcg_function_test.sh$PAGESIZE $((PAGESIZE * 2))
> <EOF>
> 
> Run LTP with the following command:
> # ./runltp -f memcg_function
> <<<test_start>>>
> tag=memcg_function stime=1271856934
> cmdline="       memcg_function_test.sh"
> contacts=""
> analysis=exit
> <<<test_output>>>
> memcg_function_test    1  TPASS  :  rss=4096/4096, cache=0/0
> memcg_function_test    2  TPASS  :  rss=0/0, cache=4096/4096
> memcg_function_test    3  TPASS  :  rss=0/0, cache=4096/4096
> memcg_function_test    4  TPASS  :  rss=4096/4096, cache=8192/8192
> memcg_function_test    5  TPASS  :  rss=4096/4096, cache=0/0
> memcg_function_test    6  TPASS  :  rss=4096/4096, cache=0/0
> memcg_function_test    6  TPASS  :  rss=0/0, cache=0/0
> memcg_function_test    7  TPASS  :  rss=0/0, cache=4096/4096
> memcg_function_test    7  TPASS  :  rss=0/0, cache=0/0
> memcg_function_test    8  TPASS  :  rss=0/0, cache=4096/4096
> memcg_function_test    8  TPASS  :  rss=0/0, cache=0/0
> memcg_function_test    9  TFAIL  :  rss=8192/4096, cache=8192/8192
> memcg_function_test    9  TFAIL  :  rss=4096/0, cache=0/0
> memcg_function_test   10  TPASS  :  rss=4096/4096, cache=0/0
> memcg_function_test   10  TPASS  :  rss=0/0, cache=0/0
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 106: 18335 Killed          
>        $TEST_PATH/memcg_process $1 -s $2
> memcg_function_test   11  TPASS  :  failcnt=8
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 106: 18351 Killed          
>        $TEST_PATH/memcg_process $1 -s $2
> memcg_function_test   12  TPASS  :  failcnt=8
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 106: 18367 Killed          
>        $TEST_PATH/memcg_process $1 -s $2
> memcg_function_test   13  TPASS  :  failcnt=8
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18385 Killed          
>        $TEST_PATH/memcg_process $2 -s $3
> memcg_function_test   14  TPASS  :  process 18385 is killed
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18398 Killed          
>        $TEST_PATH/memcg_process $2 -s $3
> memcg_function_test   15  TPASS  :  process 18398 is killed
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18414 Killed          
>        $TEST_PATH/memcg_process $2 -s $3
> memcg_function_test   16  TPASS  :  process 18414 is killed
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18432 Killed          
>        $TEST_PATH/memcg_process $2 -s $3
> memcg_function_test   17  TPASS  :  process 18432 is killed
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18450 Killed          
>        $TEST_PATH/memcg_process $2 -s $3
> memcg_function_test   18  TPASS  :  process 18450 is killed
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18467 Killed          
>        $TEST_PATH/memcg_process $2 -s $3
> memcg_function_test   19  TPASS  :  process 18467 is killed
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18482 Killed          
>        $TEST_PATH/memcg_process $2 -s $3
> memcg_function_test   20  TPASS  :  process 18482 is killed
> /opt/ltp/testcases/bin/memcg_function_test.sh: line 143: 18495 Killed          
>        $TEST_PATH/memcg_process $2 -s $3
> memcg_function_test   21  TPASS  :  process 18495 is killed
> memcg_function_test   22  TPASS  :  input=4095, limit_in_bytes=4096
> memcg_function_test   23  TPASS  :  input=4097, limit_in_bytes=8192
> memcg_function_test   24  TPASS  :  input=1, limit_in_bytes=4096
> memcg_function_test   25  TPASS  :  return value is 0
> memcg_function_test   26  TPASS  :  return value is 1
> memcg_function_test   27  TPASS  :  return value is 1
> memcg_function_test   28  TPASS  :  return value is 1
> memcg_function_test   29  TPASS  :  force memory succeeded
> memcg_function_test   30  TPASS  :  force memory failed as expected
> memcg_function_test   31  TPASS  :  return value is 0
> memcg_function_test   32  TPASS  :  return value is 0
> memcg_function_test   33  TPASS  :  return value is 0
> memcg_function_test   34  TPASS  :  return value is 0
> memcg_function_test   35  TPASS  :  return value is 1
> memcg_function_test   36  TPASS  :  rss=4096/4096, cache=0/0
> memcg_function_test   36  TPASS  :  rss=0/0, cache=0/0
> memcg_function_test   37  TPASS  :  rss=4096/4096, cache=0/0
> memcg_function_test   37  TPASS  :  rss=0/0, cache=0/0
> memcg_function_test   38  TPASS  :  rss=4096/4096, cache=0/0
> memcg_function_test   38  TPASS  :  rss=0/0, cache=0/0
> <<<execution_status>>>
> initiation_status="ok"
> duration=110 termination_type=exited termination_id=1 corefile=no
> cutime=15 cstime=282
> <<<test_end>>>
> 
> Regards--
> Subrata
> 


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[08/12 FAILURE] LTPX clock gettime03 fails

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]

Subject: LTP�� clock_gettime03 fails

Issue Description below:
=======================================
# ./runltp -s clock_gettime03
<<<test_output>>>
clock_gettime03    1  TPASS  :  got expected failure: TEST_ERRNO=EFAULT(14):
Bad address
clock_gettime03    2  TPASS  :  got expected failure: TEST_ERRNO=EFAULT(14):
Bad address
clock_gettime03    3  TFAIL  :  failed to produce expected error [expected
errno = 22 (Invalid argument), TEST_RETURN = 0]: TEST_ERRNO=???(0): Success
clock_gettime03    4  TFAIL  :  failed to produce expected error [expected
errno = 22 (Invalid argument), TEST_RETURN = 0]: TEST_ERRNO=???(0): Success
clock_gettime03    5  TPASS  :  got expected failure: TEST_ERRNO=EFAULT(14):
Bad address
clock_gettime03    6  TPASS  :  got expected failure: TEST_ERRNO=EFAULT(14):
Bad address
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=1
<<<test_end>>>

SUZUKI K. POULOSE gave the following patch already. Not sure if it is
discussed in the mailing list:
--- include/common_timers.h.orig        2010-04-30 12:39:08.000000000 +0000
+++ include/common_timers.h     2010-04-30 12:39:46.000000000 +0000
@@ -35,7 +35,8 @@ clock_t clock_list[] = {
        CLOCK_THREAD_CPUTIME_ID,
        CLOCK_MONOTONIC_RAW,
 };
-#define MAX_CLOCKS (sizeof(clock_list) / sizeof(*clock_list))
+// #define MAX_CLOCKS (sizeof(clock_list) / sizeof(*clock_list))
+#define MAX_CLOCKS 16

 const char *get_clock_str(const int clock_id)
 {


The above patch fixes the problem. For more info, see linux/time.h for the
MAX_CLOCKS value.

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [08/12 FAILURE] LTPE clock gettime03 fails

[Suzuki Poulose]

[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]

On വ്യാഴം 06 മെയ് 2010 12:28 വൈകു, Subrata Modak wrote:
> Subject: LTPE^[ clock_gettime03 fails
>
> Issue Description below:
> =======================================
> # ./runltp -s clock_gettime03
> <<<test_output>>>
> clock_gettime03    1  TPASS  :  got expected failure: TEST_ERRNO=EFAULT(14):
> Bad address
> clock_gettime03    2  TPASS  :  got expected failure: TEST_ERRNO=EFAULT(14):
> Bad address
> clock_gettime03    3  TFAIL  :  failed to produce expected error [expected
> errno = 22 (Invalid argument), TEST_RETURN = 0]: TEST_ERRNO=???(0): Success
> clock_gettime03    4  TFAIL  :  failed to produce expected error [expected
> errno = 22 (Invalid argument), TEST_RETURN = 0]: TEST_ERRNO=???(0): Success
> clock_gettime03    5  TPASS  :  got expected failure: TEST_ERRNO=EFAULT(14):
> Bad address
> clock_gettime03    6  TPASS  :  got expected failure: TEST_ERRNO=EFAULT(14):
> Bad address
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=1 corefile=no
> cutime=0 cstime=1
> <<<test_end>>>
>
> SUZUKI K. POULOSE gave the following patch already. Not sure if it is
> discussed in the mailing list:
> --- include/common_timers.h.orig        2010-04-30 12:39:08.000000000 +0000
> +++ include/common_timers.h     2010-04-30 12:39:46.000000000 +0000
> @@ -35,7 +35,8 @@ clock_t clock_list[] = {
>          CLOCK_THREAD_CPUTIME_ID,
>          CLOCK_MONOTONIC_RAW,
>   };
> -#define MAX_CLOCKS (sizeof(clock_list) / sizeof(*clock_list))
> +// #define MAX_CLOCKS (sizeof(clock_list) / sizeof(*clock_list))
> +#define MAX_CLOCKS 16
>
>   const char *get_clock_str(const int clock_id)
>   {
>
>
> The above patch fixes the problem. For more info, see linux/time.h for the
> MAX_CLOCKS value.

The above patch indeed fixes the two issues, but it causes a regression 
for timer_create02 testcase. The complete patch is attached with this.


>
> Regards--
> Subrata
>


[-- Attachment #2: fix-timer-tests-bad-header.diff --]
[-- Type: text/plain, Size: 1730 bytes --]

The MAX_CLOCKS supported by the kernel is 16. But the kernel may not have all
the clock sources defined in the range 0-15.

Hence, to test whether kernel returns error for an INVALID clock source id,
we should use the upper limit MAX_CLOCKS (16 at the moment).

But to verify the the defined clocks work fine, we should loop through the "list"
of clock sources defined for sure. (Used as CLOCKS_DEFINED below)

Signed-off-by: Suzuki K P <suzuki@in.ibm.com>

Index: ltp/testcases/kernel/timers/include/common_timers.h
===================================================================
--- ltp.orig/testcases/kernel/timers/include/common_timers.h	2009-12-06 20:53:44.000000000 +0000
+++ ltp/testcases/kernel/timers/include/common_timers.h	2010-05-05 09:17:58.000000000 +0000
@@ -35,7 +35,10 @@
 	CLOCK_THREAD_CPUTIME_ID,
 	CLOCK_MONOTONIC_RAW,
 };
-#define MAX_CLOCKS (sizeof(clock_list) / sizeof(*clock_list))
+/* CLOCKS_DEFINED is the number of clock sources defined for sure */
+#define CLOCKS_DEFINED (sizeof(clock_list) / sizeof(*clock_list))
+/* MAX_CLOCKS is the maximum number of clock sources supported by kernel */
+#define MAX_CLOCKS 16
 
 const char *get_clock_str(const int clock_id)
 {
Index: ltp/testcases/kernel/timers/timer_create/timer_create02.c
===================================================================
--- ltp.orig/testcases/kernel/timers/timer_create/timer_create02.c	2010-05-05 09:18:21.000000000 +0000
+++ ltp/testcases/kernel/timers/timer_create/timer_create02.c	2010-05-05 09:18:38.000000000 +0000
@@ -113,7 +113,7 @@
 
 			setup_test(i);
 
-			for (j = 0; j < MAX_CLOCKS; ++j) {
+			for (j = 0; j < CLOCKS_DEFINED; ++j) {
 
 				if (strstr(get_clock_str(clock_list[j]),
 						"CPUTIME_ID")) {

[-- Attachment #3: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [08/12 FAILURE] LTPE clock gettime03 fails

[Garrett Cooper]

On May 6, 2010, at 12:04 AM, Suzuki Poulose wrote:

> <fix-timer-tests-bad-header.diff>

	Maybe a better solution would be to NULL terminate the array (well, or do similar)? Using two units of measurement just seems like it'd complicate how things are being performed...
Thanks,
-Garrett
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [08/12 FAILURE] LTPE clock gettime03 fails

[Suzuki Poulose]

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

On വ്യാഴം 06 മെയ് 2010 01:25 വൈകു, Garrett Cooper wrote:
> On May 6, 2010, at 12:04 AM, Suzuki Poulose wrote:
>
>> <fix-timer-tests-bad-header.diff>
>
> 	Maybe a better solution would be to NULL terminate the array (well, or do similar)? Using two units of measurement just seems like it'd complicate how things are being performed...

Used MAX_CLOCKS to mark the end of clock list array. Patch attached.


Thanks

Suzuki
> Thanks,
> -Garrett


[-- Attachment #2: fix-timer-tests-bad-header.diff --]
[-- Type: text/plain, Size: 1760 bytes --]

The MAX_CLOCKS supported by the kernel is 16. But the kernel may not have all
the clock sources defined in the range 0-15.

Hence, to test whether kernel returns error for an INVALID clock source id,
we should use the upper limit MAX_CLOCKS (16 at the moment).

But to verify the the defined clocks work fine, we should loop through the "list"
of clock sources defined for sure. MAX_CLOCKS marsk the end of the clock sources in the 
array.

Signed-off-by: Suzuki K P <suzuki@in.ibm.com>

Index: ltp/testcases/kernel/timers/include/common_timers.h
===================================================================
--- ltp.orig/testcases/kernel/timers/include/common_timers.h	2009-12-06 20:53:44.000000000 +0000
+++ ltp/testcases/kernel/timers/include/common_timers.h	2010-05-05 09:17:58.000000000 +0000
@@ -35,7 +35,10 @@
 	CLOCK_THREAD_CPUTIME_ID,
 	CLOCK_MONOTONIC_RAW,
 };
-#define MAX_CLOCKS (sizeof(clock_list) / sizeof(*clock_list))
+/* CLOCKS_DEFINED is the number of clock sources defined for sure */
+#define CLOCKS_DEFINED (sizeof(clock_list) / sizeof(*clock_list))
+/* MAX_CLOCKS is the maximum number of clock sources supported by kernel */
+#define MAX_CLOCKS 16
 
 const char *get_clock_str(const int clock_id)
 {
Index: ltp/testcases/kernel/timers/timer_create/timer_create02.c
===================================================================
--- ltp.orig/testcases/kernel/timers/timer_create/timer_create02.c	2010-05-05 09:18:21.000000000 +0000
+++ ltp/testcases/kernel/timers/timer_create/timer_create02.c	2010-05-05 09:18:38.000000000 +0000
@@ -113,7 +113,7 @@
 
 			setup_test(i);
 
-			for (j = 0; j < MAX_CLOCKS; ++j) {
+			for (j = 0; j < CLOCKS_DEFINED; ++j) {
 
 				if (strstr(get_clock_str(clock_list[j]),
 						"CPUTIME_ID")) {

[-- Attachment #3: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [08/12 FAILURE] LTPE clock gettime03 fails

[Garrett Cooper]

On Thu, May 6, 2010 at 2:03 AM, Suzuki Poulose <suzuki@in.ibm.com> wrote:
> On വ്യാഴം 06 മെയ് 2010 01:25 വൈകു, Garrett Cooper wrote:
>>
>> On May 6, 2010, at 12:04 AM, Suzuki Poulose wrote:
>>
>>> <fix-timer-tests-bad-header.diff>
>>
>>        Maybe a better solution would be to NULL terminate the array (well,
>> or do similar)? Using two units of measurement just seems like it'd
>> complicate how things are being performed...
>
> Used MAX_CLOCKS to mark the end of clock list array. Patch attached.

Looks good. Acked-by: Garrett Cooper <yanegomi@gmail.com>

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [08/12 FAILURE] LTPE clock gettime03 fails

[Subrata Modak]

On Thu, 2010-05-06 at 10:42 -0700, Garrett Cooper wrote:
> On Thu, May 6, 2010 at 2:03 AM, Suzuki Poulose <suzuki@in.ibm.com> wrote:
> > On വ്യാഴം 06 മെയ് 2010 01:25 വൈകു, Garrett Cooper wrote:
> >>
> >> On May 6, 2010, at 12:04 AM, Suzuki Poulose wrote:
> >>
> >>> <fix-timer-tests-bad-header.diff>
> >>
> >>        Maybe a better solution would be to NULL terminate the array (well,
> >> or do similar)? Using two units of measurement just seems like it'd
> >> complicate how things are being performed...
> >
> > Used MAX_CLOCKS to mark the end of clock list array. Patch attached.
> 
> Looks good. Acked-by: Garrett Cooper <yanegomi@gmail.com>

Ok. Done.

Regards--
Subrata



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

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [08/12 FAILURE] LTPE clock gettime03 fails

[Suzuki Poulose]

[-- Attachment #1: Type: text/plain, Size: 704 bytes --]

On വ്യാഴം 06 മെയ് 2010 02:33 വൈകു, Suzuki Poulose wrote:
> On വ്യാഴം 06 മെയ് 2010 01:25 വൈകു, Garrett Cooper wrote:
>> On May 6, 2010, at 12:04 AM, Suzuki Poulose wrote:
>>
>>> <fix-timer-tests-bad-header.diff>
>>
>> Maybe a better solution would be to NULL terminate the array (well, or
>> do similar)? Using two units of measurement just seems like it'd
>> complicate how things are being performed...
>
> Used MAX_CLOCKS to mark the end of clock list array. Patch attached.

Just realized that, I sent the very old patch not the updated one. Here 
is the updated one:


>
>
> Thanks
>
> Suzuki
>> Thanks,
>> -Garrett
>


[-- Attachment #2: fix-timer-tests-bad-header.diff --]
[-- Type: text/plain, Size: 1851 bytes --]

The MAX_CLOCKS supported by the kernel is 16. But the kernel may not have all
the clock sources defined in the range 0-15.

Hence, to test whether kernel returns error for an INVALID clock source id,
we should use the upper limit MAX_CLOCKS (16 at the moment).

But to verify the the defined clocks work fine, we should loop through the "list"
of clock sources defined for sure. MAX_CLOCKS marsk the end of the clock sources in the 
array.

Signed-off-by: 	Suzuki K P <suzuki@in.ibm.com>
Cc:		Garrett Cooper <yanegomi@gmail.com>

Index: ltp/testcases/kernel/timers/include/common_timers.h
===================================================================
--- ltp.orig/testcases/kernel/timers/include/common_timers.h	2010-06-01 15:28:04.000000000 +0000
+++ ltp/testcases/kernel/timers/include/common_timers.h	2010-06-01 15:34:33.000000000 +0000
@@ -28,14 +28,18 @@
 #ifndef CLOCK_MONOTONIC_RAW
 #define CLOCK_MONOTONIC_RAW 4
 #endif
+
+/* MAX_CLOCKS is the maximum number of clock sources supported by kernel */
+#define MAX_CLOCKS 16
+
 clock_t clock_list[] = {
 	CLOCK_REALTIME,
 	CLOCK_MONOTONIC,
 	CLOCK_PROCESS_CPUTIME_ID,
 	CLOCK_THREAD_CPUTIME_ID,
 	CLOCK_MONOTONIC_RAW,
+	MAX_CLOCKS
 };
-#define MAX_CLOCKS (sizeof(clock_list) / sizeof(*clock_list))
 
 const char *get_clock_str(const int clock_id)
 {
Index: ltp/testcases/kernel/timers/timer_create/timer_create02.c
===================================================================
--- ltp.orig/testcases/kernel/timers/timer_create/timer_create02.c	2010-06-01 15:28:04.000000000 +0000
+++ ltp/testcases/kernel/timers/timer_create/timer_create02.c	2010-06-01 15:34:56.000000000 +0000
@@ -113,7 +113,7 @@
 
 			setup_test(i);
 
-			for (j = 0; j < MAX_CLOCKS; ++j) {
+			for (j = 0; clock_list[j] != MAX_CLOCKS; ++j) {
 
 				if (strstr(get_clock_str(clock_list[j]),
 						"CPUTIME_ID")) {

[-- Attachment #3: Type: text/plain, Size: 80 bytes --]

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


[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [08/12 FAILURE] LTPE clock gettime03 fails

[Subrata Modak]

On Tue, 2010-06-01 at 21:10 +0530, Suzuki Poulose wrote: 
> On വ്യാഴം 06 മെയ് 2010 02:33 വൈകു, Suzuki Poulose wrote:
> > On വ്യാഴം 06 മെയ് 2010 01:25 വൈകു, Garrett Cooper wrote:
> >> On May 6, 2010, at 12:04 AM, Suzuki Poulose wrote:
> >>
> >>> <fix-timer-tests-bad-header.diff>
> >>
> >> Maybe a better solution would be to NULL terminate the array (well, or
> >> do similar)? Using two units of measurement just seems like it'd
> >> complicate how things are being performed...
> >
> > Used MAX_CLOCKS to mark the end of clock list array. Patch attached.
> 
> Just realized that, I sent the very old patch not the updated one. Here 
> is the updated one:

Seems like i was not able to apply the new one even after reverting the
old one back. Can you please rebase and resend :-(

Regards--
Subrata

> 
> 
> >
> >
> > Thanks
> >
> > Suzuki
> >> Thanks,
> >> -Garrett
> >
> 


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

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [08/12 FAILURE] LTPE clock gettime03 fails

[Subrata Modak]

This also is resolved now.

Regards--
Subrata

On Wed, 2010-06-02 at 18:27 +0530, Subrata Modak wrote:
> On Tue, 2010-06-01 at 21:10 +0530, Suzuki Poulose wrote: 
> > On വ്യാഴം 06 മെയ് 2010 02:33 വൈകു, Suzuki Poulose wrote:
> > > On വ്യാഴം 06 മെയ് 2010 01:25 വൈകു, Garrett Cooper wrote:
> > >> On May 6, 2010, at 12:04 AM, Suzuki Poulose wrote:
> > >>
> > >>> <fix-timer-tests-bad-header.diff>
> > >>
> > >> Maybe a better solution would be to NULL terminate the array (well, or
> > >> do similar)? Using two units of measurement just seems like it'd
> > >> complicate how things are being performed...
> > >
> > > Used MAX_CLOCKS to mark the end of clock list array. Patch attached.
> > 
> > Just realized that, I sent the very old patch not the updated one. Here 
> > is the updated one:
> 
> Seems like i was not able to apply the new one even after reverting the
> old one back. Can you please rebase and resend :-(
> 
> Regards--
> Subrata
> 
> > 
> > 
> > >
> > >
> > > Thanks
> > >
> > > Suzuki
> > >> Thanks,
> > >> -Garrett
> > >
> > 
> 
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[09/12 FAILURE] LTPX timer create04 fails

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Subject: LTP�� timer_create04 fails

Issues Description below:
=======================================
# ./runltp -s timer_create04
<<<test_output>>>
timer_create04    1  TFAIL  :  didn't fail as expected [expected errno = 22
(Invalid argument)]: TEST_ERRNO=???(95): Operation not supported
timer_create04    2  TFAIL  :  didn't fail as expected [expected errno = 22
(Invalid argument)]: TEST_ERRNO=???(95): Operation not supported
timer_create04    3  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
address
timer_create04    4  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
address
timer_create04    5  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
address
timer_create04    6  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
address
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>

SUZUKI K. POULOSE said that the same patch for issue #8 will solve the problem :-)

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [09/12 FAILURE] LTP timer create04 fails

[Henry xu]

在 2010-05-06四的 12:28 +0530，Subrata Modak写道：
> Subject: LTPś timer_create04 fails
> 
> Issues Description below:
> =======================================
> # ./runltp -s timer_create04
> <<<test_output>>>
> timer_create04    1  TFAIL  :  didn't fail as expected [expected errno = 22
> (Invalid argument)]: TEST_ERRNO=???(95): Operation not supported
> timer_create04    2  TFAIL  :  didn't fail as expected [expected errno = 22
> (Invalid argument)]: TEST_ERRNO=???(95): Operation not supported

I think the FAILs are caused by MAX_CLOCKS in common_timers.h not equal
to MAX_CLOCKS in kernel.If equality,the case can be passed.

regards

> timer_create04    3  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
> address
> timer_create04    4  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
> address
> timer_create04    5  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
> address
> timer_create04    6  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
> address
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=1 corefile=no
> cutime=0 cstime=0
> <<<test_end>>>
> 
> SUZUKI K. POULOSE said that the same patch for issue #8 will solve the problem :-)
> 
> Regards--
> Subrata
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list

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

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [09/12 FAILURE] LTPE timer create04 fails

[Subrata Modak]

Fixed now with Latest LTP.

Regards--
Subrata

On Thu, 2010-05-06 at 12:28 +0530, Subrata Modak wrote:
> Subject: LTPE^[ timer_create04 fails
> 
> Issues Description below:
> =======================================
> # ./runltp -s timer_create04
> <<<test_output>>>
> timer_create04    1  TFAIL  :  didn't fail as expected [expected errno = 22
> (Invalid argument)]: TEST_ERRNO=???(95): Operation not supported
> timer_create04    2  TFAIL  :  didn't fail as expected [expected errno = 22
> (Invalid argument)]: TEST_ERRNO=???(95): Operation not supported
> timer_create04    3  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
> address
> timer_create04    4  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
> address
> timer_create04    5  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
> address
> timer_create04    6  TPASS  :  failed as expected: TEST_ERRNO=EFAULT(14): Bad
> address
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=1 corefile=no
> cutime=0 cstime=0
> <<<test_end>>>
> 
> SUZUKI K. POULOSE said that the same patch for issue #8 will solve the problem :-)
> 
> Regards--
> Subrata
> 


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[10/12 FAILURE] LTPX ar01 fails

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]

Subject: LTP�� ar01 fails

Issue Description Below:
===============================
# vi runtest/ar01
ar export TCdat=$LTPROOT/testcases/bin; ar01
<EOF>

Run LTP with the following command:
# ./runltp -f ar01
<<<test_start>>>
tag=ar stime=1272004502
cmdline="export TCdat=$LTPROOT/testcases/bin; ar01"
contacts=""
analysis=exit
<<<test_output>>>
-------System test for ar command, Loop 1----
-)1
-)2
-)3
-)4
-)5
-)6
-)7
-)8
-)9
-)10
-)11
-)12
-)13
-)14
-)15
-)16
-)17 SKIPPED due to binutils ar automatically adds a symbol.
-)18
-)19 SKIPPED due to binutils ar automatically adds a symbol.
-)20
-)21
4,6c4,6
< -rwxrwxr-x.;0/0;17;Apr;23;12:05;file1.in
< -rwxrwxr-x.;0/0;17;Apr;23;12:05;file2.in
< -rwxrwxr-x.;0/0;19;Apr;23;12:05;file3.in
---
> -rwxrwxr-x;0/0;17;Apr;23;12:05;file1.in
> -rwxrwxr-x;0/0;17;Apr;23;12:05;file2.in
> -rwxrwxr-x;0/0;19;Apr;23;12:05;file3.in
FAIL - ar with -v failed to produce a verbose out put
-)23
-)24
-)25
-)26 SKIPPED UNDER PAN
ar: creating /tmp/ar01-9909/lib.a
-)27
ar: creating /tmp/ar01-9909/lib.a
-)28
ar: creating /tmp/ar01-9909/lib.a
-)29
ar: creating /tmp/ar01-9909/lib.a
-)30
ar: creating /tmp/ar01-9909/lib.a
-)31
---------------ar command failed the system test-----------------
<<<execution_status>>>
initiation_status="ok"
duration=6 termination_type=exited termination_id=1 corefile=no
cutime=8 cstime=50
<<<test_end>>>

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[11/12 FAILURE] LTPX file test fails

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

Subject: LTP�� file_test fails

Issues Description below:
====================================
# vi runtest/file_test
file export TCdat=$LTPROOT/testcases/bin; file_test.sh
<EOF>

Run LTP with the following command:
# ./runltp -f file_test
<<<test_output>>>
file01      0  TINFO  :  TEST #1: file command recogizes ASCII text files
file01      1  TPASS  :  file: Recognised ASCII file correctly
file02      0  TINFO  :  TEST #2: file command recognizes bash shell scripts
file02      2  TPASS  :  file: Recognised bash shell script correctly
file03      0  TINFO  :  TEST #3: file command recognizes korn shell scripts
file03      3  TPASS  :  file: recognised korn shell script
file04      0  TINFO  :  TEST #4: file command recognizes C shell scripts
file04      4  TPASS  :  file: Recognised C shell script correctly
file05      0  TINFO  :  TEST #5: file command recognizes C programs text
file05      5  TPASS  :  file: Recognised C program text correctly
file06      0  TINFO  :  TEST #6: file command recognizes ELF executables
file06      6  TPASS  :  file: Recognized ELF binary executable
file07      0  TINFO  :  TEST #7: file command recognizes tar files.
file07      7  TPASS  :  file: Recognised tar files
file08      0  TINFO  :  TEST #8: file command recognizes tar zip files
file08      8  TPASS  :  file: Recognised tar zip file
file09      0  TINFO  :  TEST #9: file command recognizes RPM files
file09      9  TFAIL  :  file: Failed to Recognize RPM file. Reason:
/root/rpmbuild/SRPMS/cprog-0.0.7-3.src.rpm: RPM v3.0 src
file10      0  TINFO  :  TEST #10: file command recognizes vmlinu file
file10     10  TPASS  :  file: Recognised vmlinu file correctly
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=7 cstime=18
<<<test_end>>>

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [11/12 FAILURE] LTP? file test fails

[Garrett Cooper]

[-- Attachment #1.1: Type: text/plain, Size: 2181 bytes --]

On May 5, 2010, at 11:58 PM, Subrata Modak wrote:

> Subject: LTPś file_test fails
> 
> Issues Description below:
> ====================================
> # vi runtest/file_test
> file export TCdat=$LTPROOT/testcases/bin; file_test.sh
> <EOF>
> 
> Run LTP with the following command:
> # ./runltp -f file_test
> <<<test_output>>>
> file01      0  TINFO  :  TEST #1: file command recogizes ASCII text files
> file01      1  TPASS  :  file: Recognised ASCII file correctly
> file02      0  TINFO  :  TEST #2: file command recognizes bash shell scripts
> file02      2  TPASS  :  file: Recognised bash shell script correctly
> file03      0  TINFO  :  TEST #3: file command recognizes korn shell scripts
> file03      3  TPASS  :  file: recognised korn shell script
> file04      0  TINFO  :  TEST #4: file command recognizes C shell scripts
> file04      4  TPASS  :  file: Recognised C shell script correctly
> file05      0  TINFO  :  TEST #5: file command recognizes C programs text
> file05      5  TPASS  :  file: Recognised C program text correctly
> file06      0  TINFO  :  TEST #6: file command recognizes ELF executables
> file06      6  TPASS  :  file: Recognized ELF binary executable
> file07      0  TINFO  :  TEST #7: file command recognizes tar files.
> file07      7  TPASS  :  file: Recognised tar files
> file08      0  TINFO  :  TEST #8: file command recognizes tar zip files
> file08      8  TPASS  :  file: Recognised tar zip file
> file09      0  TINFO  :  TEST #9: file command recognizes RPM files
> file09      9  TFAIL  :  file: Failed to Recognize RPM file. Reason:
> /root/rpmbuild/SRPMS/cprog-0.0.7-3.src.rpm: RPM v3.0 src
> file10      0  TINFO  :  TEST #10: file command recognizes vmlinu file
> file10     10  TPASS  :  file: Recognised vmlinu file correctly
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=1 corefile=no
> cutime=7 cstime=18
> <<<test_end>>>

	This is why:

	grep "RPM v3 src" $LTPTMP/file.out > /dev/null 2>&1

	change that to

	egrep "RPM v3(\.0)? src" $LTPTMP/file.out > /dev/null 2>&1

    -- that should work.
HTH,
-Garrett

[-- Attachment #1.2: Type: text/html, Size: 5228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[12/12 FAILURE] LTPX cron tests fails

[Subrata Modak]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2481 bytes --]

Subject: LTP�� cron_tests fails

Issues Description Below:
========================================
# vi runtest/cron_tests
cron_tests export TCdat=$LTPROOT/testcases/bin; cron_tests.sh
<EOF>

Run LTP with the following command:
# ./runltp -f cron_tests
<<<test_start>>>
tag=cron stime=1272004510
cmdline="export TCdat=$LTPROOT/testcases/bin; cron_tests.sh"
contacts=""
analysis=exit
<<<test_output>>>
cron01      0  TINFO  :  Test #1: crontab <filename> installs the crontab file
cron01      0  TINFO  :  Test #1: cron schedules the job listed in crontab
file.
cron01      0  TINFO  :  Test #1: Installing cron job ...
cron01      0  TINFO  :  Test #1: Cronjob installed successfully
cron01      0  TINFO  :  Test #1: /var/log/cron: Trying altenate log...
cron01      1  TFAIL  :  Test #1: crontab activity not recorded in
/var/log/messages.
cron01      0  TINFO  :  Test #1: Values are good:
    Expected 8;     Received 8
cron01      0  TINFO  :  Test #1: Values are good:
    Expected 9;     Received 9
cron01      0  TINFO  :  Test #1: Values are good:
    Expected 10;     Received 10
cron01      0  TINFO  :  Test #1: Values are good:
    Expected 11;     Received 11
cron01      0  TINFO  :  Test #1: Values are good:
    Expected 12;     Received 12
cron01      0  TINFO  :  Test #1: /var/log/cron: alternate...
cron01      1  TFAIL  :  Test #1: Test failed. Reason:
cron02      0  TINFO  :  Test #2: crontab -r removes the crontab file.
cron02      0  TINFO  :  Test #2: installing crontab file.
cron02      0  TINFO  :  Test #1: /var/log/cron: alternate...
cron02      2  TFAIL  :  Test #2: crontab activity not recorded in
var/log/messages.
cron02      0  TINFO  :  Test #2: uninstalling crontab file.
cron02      0  TINFO  :  Test #1: /var/log/cron: alternate...
cron02      2  TFAIL  :  Test #2: crontab activity not recorded in
var/log/messages.
cron03      0  TINFO  :  Test #3: crontab -l lists the cronjobs installed
cron03      0  TINFO  :  Test #3: installing crontab file ...
cron03      0  TINFO  :  Test #3: Cron job installed.
cron03      0  TINFO  :  Test #3: crontab -l listed cronjob tst2_cronprg.sh
cron03      0  TINFO  :  Test #3: uninstalling crontab file.
cron03      0  TINFO  :  crontab uninstalled all jobs for user
cron03      3  TPASS  :  crontab did not list any cronjobs
<<<execution_status>>>
initiation_status="ok"
duration=434 termination_type=exited termination_id=4 corefile=no
cutime=3 cstime=22
<<<test_end>>>

Regards--
Subrata



[-- Attachment #2: Type: text/plain, Size: 79 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list