[Canonical-ubuntu-qa] [Bug 2078315] [NEW] creat07, execve04, ioctl_loop02, ioctl_loop06, ioctl_loop07 from ubuntu_ltp_syscalls failed on N-OEM-6.11

2024-08-29 Thread Po-Hsu Lin
Public bug reported:

Issue found on 6.11.0-1001.1

Investigation shows that we will need to update our LTP fork to the following 
commits:
 * creat07, execve04
   - 12588eee syscalls/execve04,creat07: skip for kernels 6.11 and later 
 * ioctl_loop02, ioctl_loop06, ioctl_loop07
   - c02d8ddc lib: make tst_detach_device_by_fd() also close dev_fd

Test output:
COMMAND:/opt/ltp-upstream/bin/ltp-pan   -e -S   -a 147118 -n 147118 -p 
-f /tmp/ltp-qq6AS8PjLk/alltests -l 
/opt/ltp-upstream/results/LTP_RUN_ON-2024_08_29-07h_19m_37s.log  -C 
/opt/ltp-upstream/output/LTP_RUN_ON-2024_08_29-07h_19m_37s.failed -T 
/opt/ltp-upstream/output/LTP_RUN_ON-2024_08_29-07h_19m_37s.tconf
LOG File: /opt/ltp-upstream/results/LTP_RUN_ON-2024_08_29-07h_19m_37s.log
FAILED COMMAND File: 
/opt/ltp-upstream/output/LTP_RUN_ON-2024_08_29-07h_19m_37s.failed
TCONF COMMAND File: 
/opt/ltp-upstream/output/LTP_RUN_ON-2024_08_29-07h_19m_37s.tconf
Running tests...
<<>>
tag=creat07 stime=1724915977
cmdline="creat07"
contacts=""
analysis=exit
<<>>
tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3
tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s
creat07.c:37: TFAIL: creat() succeeded unexpectedly
Test timeouted, sending SIGKILL!
tst_test.c:1698: TINFO: Killed the leftover descendant processes
tst_test.c:1704: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
tst_test.c:1706: TBROK: Test killed! (timeout?)

Summary:
passed   0
failed   1
broken   1
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=30 termination_type=exited termination_id=3 corefile=no
cutime=0 cstime=0
<<>>
<<>>
tag=execve04 stime=1724916007
cmdline="execve04"
contacts=""
analysis=exit
<<>>
tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3
tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s
execve_child.c:27: TFAIL: execve_child shouldn't be executed
tst_test.c:1698: TINFO: Killed the leftover descendant processes

Summary:
passed   0
failed   1
broken   0
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=1
<<>>
<<>>
tag=ioctl_loop02 stime=1724916007
cmdline="ioctl_loop02"
contacts=""
analysis=exit
<<>>
tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3
tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s
tst_device.c:96: TINFO: Found free device 0 '/dev/loop0'
tst_buffers.c:57: TINFO: Test is using guarded buffers
ioctl_loop02.c:56: TINFO: Using LOOP_SET_FD to setup loopdevice
ioctl_loop02.c:67: TPASS: /sys/block/loop0/ro = 1
ioctl_loop02.c:68: TPASS: /sys/block/loop0/loop/backing_file = 
'/tmp/ltp-qq6AS8PjLk/LTP_iocWAhE0P/test.img'
ioctl_loop02.c:77: TPASS: lo_flags only has default LO_FLAGS_READ_ONLY flag
ioctl_loop02.c:83: TPASS: Can not write data in RO mode: EPERM (1)
ioctl_loop02.c:89: TPASS: LOOP_CHANGE_FD succeeded
ioctl_loop02.c:90: TPASS: /sys/block/loop0/ro = 1
ioctl_loop02.c:91: TPASS: /sys/block/loop0/loop/backing_file = 
'/tmp/ltp-qq6AS8PjLk/LTP_iocWAhE0P/test1.img'
ioctl_loop02.c:97: TPASS: LOOP_CHANGE_FD failed as expected: EINVAL (22)
ioctl_loop02.c:56: TINFO: Using LOOP_CONFIGURE with read_only flag
ioctl_loop02.c:63: TBROK: ioctl(5,(0x4C0A),...) failed: EBUSY (16)

Summary:
passed   8
failed   0
broken   1
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=2 corefile=no
cutime=0 cstime=0
<<>>
<<>>
tag=ioctl_loop06 stime=1724916007
cmdline="ioctl_loop06"
contacts=""
analysis=exit
<<>>
tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3
tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s
tst_device.c:96: TINFO: Found free device 0 '/dev/loop0'
ioctl_loop06.c:74: TINFO: Using LOOP_SET_BLOCK_SIZE with arg < 512
ioctl_loop06.c:65: TPASS: Set block size failed as expected: EINVAL (22)
ioctl_loop06.c:74: TINFO: Using LOOP_SET_BLOCK_SIZE with arg > PAGE_SIZE
ioctl_loop06.c:65: TPASS: Set block size failed as expected: EINVAL (22)
ioctl_loop06.c:74: TINFO: Using LOOP_SET_BLOCK_SIZE with arg != power_of_2
ioctl_loop06.c:65: TPASS: Set block size failed as expected: EINVAL (22)
ioctl_loop06.c:74: TINFO: Using LOOP_CONFIGURE with block_size < 512
ioctl_loop06.c:67: TFAIL: Set block size failed expected EINVAL got: EBUSY (16)
ioctl_loop06.c:74: TINFO: Using LOOP_CONFIGURE with block_size > PAGE_SIZE
ioctl_loop06.c:67: TFAIL: Set block size failed expected EINVAL got: EBUSY (16)
ioctl_loop06.c:74: TINFO: Using LOOP_CONFIGURE with block_size != power_of_2
ioctl_loop06.c:67: TFAIL: Set block size failed expected EINVAL got: EBUSY (16)

Summary:
passed   3
failed   3
broken   0
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<>>
<<>>
tag=ioctl_loop07 stime=1724916007
cmdline="ioctl_loop07"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3
tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s
tst_device.c:96: TINF

[Canonical-ubuntu-qa] [Bug 2078336] [NEW] VisionFive 2 Pinout link is broken

2024-08-29 Thread Dominik Viererbe
Public bug reported:

The link [1] for the pinout of the VisionFive 2 board of the testcase "Install 
VisionFive 2 in Ubuntu 
Server riscv64+visionfive2 in Noble Daily" [2] is broken (redirects to a not 
found page).

I found another manual on the internet that described the pinout [3].

[1] 
https://rvspace.org/en/Product/VisionFive/Technical_Documents/VisionFive_Single_Board_Computer_Quick_Start_Guide
[2] 
https://iso.qa.ubuntu.com/qatracker/milestones/460/builds/311644/testcases/1780/results
[3] 
https://www.manualslib.com/manual/3063600/Starfire-Visionfive-2.html?page=22#manual

** Affects: ubuntu-manual-tests
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu Manual Tests.
https://bugs.launchpad.net/bugs/2078336

Title:
  VisionFive 2 Pinout link is broken

Status in Ubuntu Manual Tests:
  New

Bug description:
  The link [1] for the pinout of the VisionFive 2 board of the testcase 
"Install VisionFive 2 in Ubuntu 
  Server riscv64+visionfive2 in Noble Daily" [2] is broken (redirects to a not 
found page).

  I found another manual on the internet that described the pinout [3].

  [1] 
https://rvspace.org/en/Product/VisionFive/Technical_Documents/VisionFive_Single_Board_Computer_Quick_Start_Guide
  [2] 
https://iso.qa.ubuntu.com/qatracker/milestones/460/builds/311644/testcases/1780/results
  [3] 
https://www.manualslib.com/manual/3063600/Starfire-Visionfive-2.html?page=22#manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/2078336/+subscriptions


-- 
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help   : https://help.launchpad.net/ListHelp


[Canonical-ubuntu-qa] [Bug 2078038] Re: UBSAN array-index-out-of-bounds reported with N-6.8 on P9 node baltar

2024-08-29 Thread Juerg Haefliger
Can you try this kernel? https://people.canonical.com/~juergh/lp2078038/

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2078038

Title:
  UBSAN array-index-out-of-bounds reported with N-6.8 on P9 node baltar

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  Issue found with Noble 6.8.0-41-generic on P9 node baltar.

  [1.628868] i40e 0002:01:00.0: enabling device (0140 -> 0142)
  [1.631444] [ cut here ]
  [1.631460] UBSAN: array-index-out-of-bounds in 
/build/linux-k1IV9m/linux-6.8.0/drivers/scsi/aacraid/comminit.c:130:16
  [1.631497] index 1 is out of range for type '_rrq [1]'
  [1.631526] CPU: 0 PID: 974 Comm: kworker/0:2 Not tainted 6.8.0-41-generic 
#41-Ubuntu
  [1.631551] Hardware name: 9006-12C POWER9 0x4e1202 opal:skiboot-v6.0.19 
PowerNV
  [1.631587] Workqueue: events work_for_cpu_fn
  [1.631621] Call Trace:
  [1.631628] [cdf938c0] [c16bfec8] 
dump_stack_lvl+0x80/0x10c (unreliable)
  [1.631663] [cdf938f0] [c0c83458] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [1.631699] [cdf939a0] [c0080c460a28] 
aac_alloc_comm.constprop.0+0x580/0x620 [aacraid]
  [1.631742] [cdf93a80] [c0080c460b18] aac_comm_init+0x50/0x4f0 
[aacraid]
  [1.631776] [cdf93b10] [c0080c4616ec] 
aac_init_adapter+0x234/0x660 [aacraid]
  [1.631808] [cdf93c10] [c0080c46ee0c] 
aac_srcv_init+0x28c/0x7b4 [aacraid]
  [1.631844] [cdf93ce0] [c0080c45395c] 
aac_probe_one+0x334/0x924 [aacraid]
  [1.631882] [cdf93da0] [c0cef564] 
local_pci_probe+0x68/0x124
  [1.631919] [cdf93e20] [c01c224c] work_for_cpu_fn+0x38/0x60
  [1.631957] [cdf93e50] [c01c8ab8] 
process_one_work+0x1d4/0x4dc
  [1.631993] [cdf93ef0] [c01ca60c] worker_thread+0x470/0x648
  [1.632031] [cdf93f90] [c01d90bc] kthread+0x138/0x140
  [1.632068] [cdf93fe0] [c000ded8] 
start_kernel_thread+0x14/0x18
  [1.632109] ---[ end trace ]---
  [1.632128] [ cut here ]
  [1.632147] UBSAN: array-index-out-of-bounds in 
/build/linux-k1IV9m/linux-6.8.0/drivers/scsi/aacraid/comminit.c:132:16
  [1.632184] index 1 is out of range for type '_rrq [1]'
  [1.632214] CPU: 0 PID: 974 Comm: kworker/0:2 Not tainted 6.8.0-41-generic 
#41-Ubuntu
  [1.632239] Hardware name: 9006-12C POWER9 0x4e1202 opal:skiboot-v6.0.19 
PowerNV
  [1.632271] Workqueue: events work_for_cpu_fn
  [1.632305] Call Trace:
  [1.632311] [cdf938c0] [c16bfec8] 
dump_stack_lvl+0x80/0x10c (unreliable)
  [1.632349] [cdf938f0] [c0c83458] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [1.632385] [cdf939a0] [c0080c460a44] 
aac_alloc_comm.constprop.0+0x59c/0x620 [aacraid]
  [1.632433] [cdf93a80] [c0080c460b18] aac_comm_init+0x50/0x4f0 
[aacraid]
  [1.632473] [cdf93b10] [c0080c4616ec] 
aac_init_adapter+0x234/0x660 [aacraid]
  [1.632511] [cdf93c10] [c0080c46ee0c] 
aac_srcv_init+0x28c/0x7b4 [aacraid]
  [1.632547] [cdf93ce0] [c0080c45395c] 
aac_probe_one+0x334/0x924 [aacraid]
  [1.632583] [cdf93da0] [c0cef564] 
local_pci_probe+0x68/0x124
  [1.632619] [cdf93e20] [c01c224c] work_for_cpu_fn+0x38/0x60
  [1.632654] [cdf93e50] [c01c8ab8] 
process_one_work+0x1d4/0x4dc
  [1.632690] [cdf93ef0] [c01ca60c] worker_thread+0x470/0x648
  [1.632728] [cdf93f90] [c01d90bc] kthread+0x138/0x140
  [1.632755] [cdf93fe0] [c000ded8] 
start_kernel_thread+0x14/0x18
  [1.632791] ---[ end trace ]---
  [1.632809] [ cut here ]
  [1.632827] UBSAN: array-index-out-of-bounds in 
/build/linux-k1IV9m/linux-6.8.0/drivers/scsi/aacraid/comminit.c:134:16
  [1.632863] index 1 is out of range for type '_rrq [1]'
  [1.632895] CPU: 0 PID: 974 Comm: kworker/0:2 Not tainted 6.8.0-41-generic 
#41-Ubuntu
  [1.632930] Hardware name: 9006-12C POWER9 0x4e1202 opal:skiboot-v6.0.19 
PowerNV
  [1.632962] Workqueue: events work_for_cpu_fn
  [1.632993] Call Trace:
  [1.633000] [cdf938c0] [c16bfec8] 
dump_stack_lvl+0x80/0x10c (unreliable)
  [1.633037] [cdf938f0] [c0c83458] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [1.633072] [cdf939a0] [c0080c460a60] 
aac_alloc_comm.constprop.0+0x5b8/0x620 [aacraid]
  [1.633112] [cdf93a80] [c0080c460b18] aac_comm_init+0x50/0x4f0 
[aacraid]
  [1.633146] [cdf93b10] [c0080c4616ec] 
aac_init_adapter+0x234/0x660 [aacraid]
  [1.633184] [c000

[Canonical-ubuntu-qa] [Bug 2071861] Re: ftrace:test.d--event--subsystem-enable.tc fails on some instances

2024-08-29 Thread Mehmet Basaran
Seen this on noble:linux-lowlatency 6.8.0-44.44.1 cloud:openstack
instance:builder-cpu2-ram4-disk20 cycle:2024.08.05

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2071861

Title:
  ftrace:test.d--event--subsystem-enable.tc fails on some instances

Status in ubuntu-kernel-tests:
  New

Bug description:
  In the 2024.06.10 SRU cycle, the ftrace:test.d--event--subsystem-
  enable.tc testcases from ubuntu_kselftests_ftrace are failing:

  === Ftrace unit tests ===
  [1] event tracing - enable/disable with subsystem level files   [FAIL]
  [2] (instance)  event tracing - enable/disable with subsystem level files 
  [FAIL]

  
  # of passed:  0
  # of failed:  2
  # of unresolved:  0
  # of untested:  0
  # of unsupported:  0
  # of xfailed:  0
  # of undefined(test bug):  0

  The relevant part from the verbose output is `fail at least fork, exec
  and exit events should be recorded`

  This was found on these kernels:
  - j:aws-fips version 5.15.0-1065.71+fips1 on the m5a.large instance.
  - j:gcp-fips version 5.15.0-1064.72+fips1 on the n2d-standard-2 instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071861/+subscriptions


-- 
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help   : https://help.launchpad.net/ListHelp


[Canonical-ubuntu-qa] [Bug 1970971] Re: ubuntu_ltp_controllers testcase memcontrol03 fails on impish/jammy

2024-08-29 Thread Mehmet Basaran
Seen this for (cycle=2024.08.05) jammy:lowlatency-hwe-6.8
6.8.0-44.44.1~22.04.1 on metal:helo-kernel.arm64, riccioli.amd64

I haven't checked the test. My suspicion is that, we wait for a process
to finish (especially if it is a throughput oriented one where
lowlatency kernels perform worse) it doesn't finish in the preallocated
time slot and has to be killed via signal.

Here is the log:

06:49:24 INFO | START   ubuntu_ltp_controllers.memcontrol03 
ubuntu_ltp_controllers.memcontrol03 timestamp=1724914164timeout=4500
localtime=Aug 29 06:49:24   
06:49:24 DEBUG| Persistent state client._record_indent now set to 2
06:49:24 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_ltp_controllers.memcontrol03', 'ubuntu_ltp_controllers.memcontrol03')
06:49:24 DEBUG| Waiting for pid 126554 for 4500 seconds
06:49:24 WARNI| System python is too old, crash handling disabled
06:49:24 INFO | Set timeout multiplier LTP_TIMEOUT_MUL=5 for memcontrol03
06:49:41 ERROR| Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
self.run_once(*args, **dargs)
  File 
"/home/ubuntu/autotest/client/tests/ubuntu_ltp_controllers/ubuntu_ltp_controllers.py",
 line 137, in run_once
print(utils.system_output(cmd, verbose=False))
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1271, in 
system_output
verbose=verbose, args=args).stdout
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
"Command returned non-zero exit status")
CmdError: Command  failed, rc=1, Command returned non-zero exit status
* Command: 
/opt/ltp/runltp -f /tmp/target -q -C /dev/null -l /dev/null -T /dev/null
Exit status: 1
Duration: 16.5242979527

stdout:
Checking for required user/group ids

'root' user id and group found.
'nobody' user id and group found.
'bin' user id and group found.
'daemon' user id and group found.
Users group found.
Sys group found.
Required users/groups exist.
no big block device was specified on commandline.
Tests which require a big block device are disabled.
You can specify it with option -z
INFO: Test start time: Thu Aug 29 06:49:24 UTC 2024
COMMAND:/opt/ltp/bin/ltp-pan -q  -e -S   -a 126558 -n 126558  -f 
/tmp/ltp-WtLCJ4uAEW/alltests -l /dev/null  -C /dev/null -T /dev/null
LOG File: /dev/null
FAILED COMMAND File: /dev/null
TCONF COMMAND File: /dev/null
Running tests...
tst_device.c:96: TINFO: Found free device 3 '/dev/loop3'
tst_test.c:1733: TINFO: LTP version: 20240524
tst_test.c:1617: TINFO: Timeout per run is 0h 02m 30s
tst_supported_fs_types.c:96: TINFO: Kernel supports ext2
tst_supported_fs_types.c:61: TINFO: mkfs.ext2 does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports ext3
tst_supported_fs_types.c:61: TINFO: mkfs.ext3 does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports ext4
tst_supported_fs_types.c:61: TINFO: mkfs.ext4 does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports xfs
tst_supported_fs_types.c:61: TINFO: mkfs.xfs does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports btrfs
tst_supported_fs_types.c:61: TINFO: mkfs.btrfs does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports bcachefs
tst_supported_fs_types.c:57: TINFO: mkfs.bcachefs does not exist
tst_supported_fs_types.c:168: TINFO: Skipping vfat as requested by the test
tst_supported_fs_types.c:168: TINFO: Skipping exfat as requested by the test
tst_supported_fs_types.c:168: TINFO: Skipping tmpfs as requested by the test
tst_test.c:1693: TINFO: === Testing on ext2 ===
tst_test.c:1106: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts=''
mke2fs 1.46.5 (30-Dec-2021)
tst_test.c:1120: TINFO: Mounting /dev/loop3 to 
/tmp/ltp-WtLCJ4uAEW/LTP_memqICcPZ/mntdir fstyp=ext2 flags=0
memcontrol03.c:144: TINFO: Child 126630 in leaf_C: Allocating pagecache: 
52428800
memcontrol03.c:144: TINFO: Child 126646 in leaf_D: Allocating pagecache: 
52428800
memcontrol03.c:144: TINFO: Child 126648 in leaf_F: Allocating pagecache: 
52428800
memcontrol03.c:107: TINFO: Child 126650 in trunk_G: Allocating anon: 155189248
memcontrol03.c:125: TFAIL: Expected child 126650 to exit(0), but instead killed 
by SIGKILL
memcontrol03.c:208: TPASS: Expect: (A/B memory.current=54591488) ~= 52428800
memcontrol03.c:214: TPASS: Expect: (A/B/C memory.current=25808896) ~= 34603008
memcontrol03.c:216: TPASS: Expect: (A/B/D memory.current=25763840) ~= 17825792
memcontrol03.c:218: TPASS: Expect: (A/B/E memory.current=0) ~= 0
memcontrol03.c:107: TINFO: Child 126651 in trunk_G: Allocating anon: 178257920
memcontrol

[Canonical-ubuntu-qa] [Bug 1989675] Re: net/tls in ubuntu_kernel_selftests failed with 5.15 / 5.19 on scobee-kernel

2024-08-29 Thread Mehmet Basaran
Seen this with jammy:linux-lowlatency-hwe-6.8 6.8.0-44.44.1~22.04.1
(cycle=2024.08.05) on openstack:scobee-kernel.arm64


09:54:20 INFO | START   ubuntu_kselftests_net.net:tls   
ubuntu_kselftests_net.net:tls   timestamp=1724925260timeout=2700
localtime=Aug 29 09:54:20   
09:54:20 DEBUG| Persistent state client._record_indent now set to 2
09:54:20 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kselftests_net.net:tls', 'ubuntu_kselftests_net.net:tls')
09:54:20 DEBUG| Waiting for pid 16139 for 2700 seconds
09:54:20 WARNI| System python is too old, crash handling disabled
09:54:20 DEBUG| Running 'make run_tests -C net TEST_PROGS=tls TEST_GEN_PROGS='' 
TEST_CUSTOM_PROGS='''
09:54:20 DEBUG| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net'
09:54:20 DEBUG| [stdout] TAP version 13
09:54:21 DEBUG| [stdout] 1..1
09:54:21 DEBUG| [stdout] # timeout set to 0
09:54:21 DEBUG| [stdout] # selftests: net: tls
09:54:21 DEBUG| [stdout] # TAP version 13
09:54:21 DEBUG| [stdout] # 1..712
09:54:21 DEBUG| [stdout] # # Starting 712 tests from 17 test cases.
09:54:21 DEBUG| [stdout] # #  RUN   tls.12_aes_gcm.recvmsg_multiple ...
09:54:21 DEBUG| [stdout] # # tls.c:879:recvmsg_multiple:Expected 
recvmsg(self->cfd, &hdr, 0) (-1) != -1 (-1)
09:54:21 DEBUG| [stdout] # # recvmsg_multiple: Test failed at step #9
09:54:21 DEBUG| [stdout] # #  FAIL  tls.12_aes_gcm.recvmsg_multiple
09:54:21 DEBUG| [stdout] # not ok 31 tls.12_aes_gcm.recvmsg_multiple
09:54:23 DEBUG| [stdout] # #  RUN   tls.13_aes_gcm.nonblocking ...
09:54:23 DEBUG| [stdout] # # tls.c:1266:nonblocking:Expected 0 (0) != eagain (0)
09:54:23 DEBUG| [stdout] # # nonblocking: Test failed at step #9
09:54:23 DEBUG| [stdout] # #  FAIL  tls.13_aes_gcm.nonblocking
09:54:23 DEBUG| [stdout] # not ok 100 tls.13_aes_gcm.nonblocking
09:54:24 DEBUG| [stdout] # #  RUN   tls.13_aes_gcm.mutliproc_writers ...
09:54:24 DEBUG| [stdout] # # tls.c:1348:mutliproc_writers:Expected res (-1) >= 
0 (0)
09:54:54 DEBUG| [stdout] # # mutliproc_writers: Test terminated by timeout
09:54:54 DEBUG| [stdout] # #  FAIL  tls.13_aes_gcm.mutliproc_writers
09:54:54 DEBUG| [stdout] # not ok 103 tls.13_aes_gcm.mutliproc_writers
09:54:54 DEBUG| [stdout] # #  RUN   
tls.13_aes_gcm.mutliproc_sendpage_readers ...
09:54:54 DEBUG| [stdout] # # tls.c:1348:mutliproc_sendpage_readers:Expected res 
(-1) >= 0 (0)
09:55:24 DEBUG| [stdout] # # mutliproc_sendpage_readers: Test terminated by 
timeout
09:55:24 DEBUG| [stdout] # #  FAIL  
tls.13_aes_gcm.mutliproc_sendpage_readers
09:55:24 DEBUG| [stdout] # not ok 105 tls.13_aes_gcm.mutliproc_sendpage_readers
09:55:42 DEBUG| [stdout] # #  RUN   tls.12_aes_ccm.recvmsg_multiple ...
09:55:42 DEBUG| [stdout] # # tls.c:879:recvmsg_multiple:Expected 
recvmsg(self->cfd, &hdr, 0) (-1) != -1 (-1)
09:55:42 DEBUG| [stdout] # # recvmsg_multiple: Test failed at step #9
09:55:42 DEBUG| [stdout] # #  FAIL  tls.12_aes_ccm.recvmsg_multiple
09:55:42 DEBUG| [stdout] # not ok 349 tls.12_aes_ccm.recvmsg_multiple
09:55:42 DEBUG| [stdout] # #  RUN   tls.12_aes_ccm.nonblocking ...
09:55:42 DEBUG| [stdout] # # tls.c:1266:nonblocking:Expected 0 (0) != eagain (0)
09:55:42 DEBUG| [stdout] # # nonblocking: Test failed at step #9
09:55:42 DEBUG| [stdout] # #  FAIL  tls.12_aes_ccm.nonblocking
09:55:42 DEBUG| [stdout] # not ok 365 tls.12_aes_ccm.nonblocking
09:55:44 DEBUG| [stdout] # #  RUN   
tls.12_aes_ccm.mutliproc_sendpage_writers ...
09:55:44 DEBUG| [stdout] # # tls.c:1348:mutliproc_sendpage_writers:Expected res 
(-1) >= 0 (0)
09:56:14 DEBUG| [stdout] # # mutliproc_sendpage_writers: Test terminated by 
timeout
09:56:14 DEBUG| [stdout] # #  FAIL  
tls.12_aes_ccm.mutliproc_sendpage_writers
09:56:14 DEBUG| [stdout] # not ok 371 tls.12_aes_ccm.mutliproc_sendpage_writers
09:56:14 DEBUG| [stdout] # #  RUN   tls.13_aes_ccm.nonblocking ...
09:56:14 DEBUG| [stdout] # # tls.c:1266:nonblocking:Expected 0 (0) != eagain (0)
09:56:14 DEBUG| [stdout] # # nonblocking: Test failed at step #9
09:56:14 DEBUG| [stdout] # #  FAIL  tls.13_aes_ccm.nonblocking
09:56:14 DEBUG| [stdout] # not ok 418 tls.13_aes_ccm.nonblocking
09:56:15 DEBUG| [stdout] # #  RUN   tls.13_aes_ccm.mutliproc_readers ...
09:56:15 DEBUG| [stdout] # # tls.c:1348:mutliproc_readers:Expected res (-1) >= 
0 (0)
09:56:45 DEBUG| [stdout] # # mutliproc_readers: Test terminated by timeout
09:56:45 DEBUG| [stdout] # #  FAIL  tls.13_aes_ccm.mutliproc_readers
09:56:45 DEBUG| [stdout] # not ok 420 tls.13_aes_ccm.mutliproc_readers
09:56:46 DEBUG| [stdout] # #  RUN   tls.12_aes_gcm_256.recvmsg_multiple 
...
09:56:46 DEBUG| [stdout] # # tls.c:879:recvmsg_multiple:Expected 
recvmsg(self->cfd, &hdr, 0) (-1) != -1 (-1)
09:56:46 DEBUG| [stdout] # # recvmsg_multiple: Test failed at step #9
09:56:46 DEBUG| [stdout

[Canonical-ubuntu-qa] [Bug 2078038] Re: UBSAN array-index-out-of-bounds reported with N-6.8 on P9 node baltar

2024-08-29 Thread Po-Hsu Lin
Sure, I will test it once the hardware is free.

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2078038

Title:
  UBSAN array-index-out-of-bounds reported with N-6.8 on P9 node baltar

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  Issue found with Noble 6.8.0-41-generic on P9 node baltar.

  [1.628868] i40e 0002:01:00.0: enabling device (0140 -> 0142)
  [1.631444] [ cut here ]
  [1.631460] UBSAN: array-index-out-of-bounds in 
/build/linux-k1IV9m/linux-6.8.0/drivers/scsi/aacraid/comminit.c:130:16
  [1.631497] index 1 is out of range for type '_rrq [1]'
  [1.631526] CPU: 0 PID: 974 Comm: kworker/0:2 Not tainted 6.8.0-41-generic 
#41-Ubuntu
  [1.631551] Hardware name: 9006-12C POWER9 0x4e1202 opal:skiboot-v6.0.19 
PowerNV
  [1.631587] Workqueue: events work_for_cpu_fn
  [1.631621] Call Trace:
  [1.631628] [cdf938c0] [c16bfec8] 
dump_stack_lvl+0x80/0x10c (unreliable)
  [1.631663] [cdf938f0] [c0c83458] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [1.631699] [cdf939a0] [c0080c460a28] 
aac_alloc_comm.constprop.0+0x580/0x620 [aacraid]
  [1.631742] [cdf93a80] [c0080c460b18] aac_comm_init+0x50/0x4f0 
[aacraid]
  [1.631776] [cdf93b10] [c0080c4616ec] 
aac_init_adapter+0x234/0x660 [aacraid]
  [1.631808] [cdf93c10] [c0080c46ee0c] 
aac_srcv_init+0x28c/0x7b4 [aacraid]
  [1.631844] [cdf93ce0] [c0080c45395c] 
aac_probe_one+0x334/0x924 [aacraid]
  [1.631882] [cdf93da0] [c0cef564] 
local_pci_probe+0x68/0x124
  [1.631919] [cdf93e20] [c01c224c] work_for_cpu_fn+0x38/0x60
  [1.631957] [cdf93e50] [c01c8ab8] 
process_one_work+0x1d4/0x4dc
  [1.631993] [cdf93ef0] [c01ca60c] worker_thread+0x470/0x648
  [1.632031] [cdf93f90] [c01d90bc] kthread+0x138/0x140
  [1.632068] [cdf93fe0] [c000ded8] 
start_kernel_thread+0x14/0x18
  [1.632109] ---[ end trace ]---
  [1.632128] [ cut here ]
  [1.632147] UBSAN: array-index-out-of-bounds in 
/build/linux-k1IV9m/linux-6.8.0/drivers/scsi/aacraid/comminit.c:132:16
  [1.632184] index 1 is out of range for type '_rrq [1]'
  [1.632214] CPU: 0 PID: 974 Comm: kworker/0:2 Not tainted 6.8.0-41-generic 
#41-Ubuntu
  [1.632239] Hardware name: 9006-12C POWER9 0x4e1202 opal:skiboot-v6.0.19 
PowerNV
  [1.632271] Workqueue: events work_for_cpu_fn
  [1.632305] Call Trace:
  [1.632311] [cdf938c0] [c16bfec8] 
dump_stack_lvl+0x80/0x10c (unreliable)
  [1.632349] [cdf938f0] [c0c83458] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [1.632385] [cdf939a0] [c0080c460a44] 
aac_alloc_comm.constprop.0+0x59c/0x620 [aacraid]
  [1.632433] [cdf93a80] [c0080c460b18] aac_comm_init+0x50/0x4f0 
[aacraid]
  [1.632473] [cdf93b10] [c0080c4616ec] 
aac_init_adapter+0x234/0x660 [aacraid]
  [1.632511] [cdf93c10] [c0080c46ee0c] 
aac_srcv_init+0x28c/0x7b4 [aacraid]
  [1.632547] [cdf93ce0] [c0080c45395c] 
aac_probe_one+0x334/0x924 [aacraid]
  [1.632583] [cdf93da0] [c0cef564] 
local_pci_probe+0x68/0x124
  [1.632619] [cdf93e20] [c01c224c] work_for_cpu_fn+0x38/0x60
  [1.632654] [cdf93e50] [c01c8ab8] 
process_one_work+0x1d4/0x4dc
  [1.632690] [cdf93ef0] [c01ca60c] worker_thread+0x470/0x648
  [1.632728] [cdf93f90] [c01d90bc] kthread+0x138/0x140
  [1.632755] [cdf93fe0] [c000ded8] 
start_kernel_thread+0x14/0x18
  [1.632791] ---[ end trace ]---
  [1.632809] [ cut here ]
  [1.632827] UBSAN: array-index-out-of-bounds in 
/build/linux-k1IV9m/linux-6.8.0/drivers/scsi/aacraid/comminit.c:134:16
  [1.632863] index 1 is out of range for type '_rrq [1]'
  [1.632895] CPU: 0 PID: 974 Comm: kworker/0:2 Not tainted 6.8.0-41-generic 
#41-Ubuntu
  [1.632930] Hardware name: 9006-12C POWER9 0x4e1202 opal:skiboot-v6.0.19 
PowerNV
  [1.632962] Workqueue: events work_for_cpu_fn
  [1.632993] Call Trace:
  [1.633000] [cdf938c0] [c16bfec8] 
dump_stack_lvl+0x80/0x10c (unreliable)
  [1.633037] [cdf938f0] [c0c83458] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [1.633072] [cdf939a0] [c0080c460a60] 
aac_alloc_comm.constprop.0+0x5b8/0x620 [aacraid]
  [1.633112] [cdf93a80] [c0080c460b18] aac_comm_init+0x50/0x4f0 
[aacraid]
  [1.633146] [cdf93b10] [c0080c4616ec] 
aac_init_adapter+0x234/0x660 [aacraid]
  [1.633184] [cdf93c10] [c0080c