copy_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3

Bug #1851653 reported by Po-Hsu Lin on 2019-11-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned

Bug Description

copy_file_range02 from ubuntu_ltp_syscalls failed on i386 node pepe with B-hwe-edge 5.3 kernel

Test failed with:
    copy_file_range02.c:141: FAIL: copy_file_range failed unexpectedly; expected EOVERFLOW, but got: EFBIG (27)

Test output:
 startup='Thu Nov 7 09:22:16 2019'
 tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0'
 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
 mke2fs 1.44.1 (24-Mar-2018)
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 copy_file_range.h:36: INFO: Testing libc copy_file_range()
 tst_device.c:87: INFO: Found free device 1 '/dev/loop1'
 Setting up swapspace version 1, size = 36 KiB (36864 bytes)
 no label, UUID=d68e7005-a932-41eb-a444-3aff47d5cf84
 copy_file_range02.c:108: INFO: Test #0: readonly file
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9)
 copy_file_range02.c:108: INFO: Test #1: directory
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EISDIR (21)
 copy_file_range02.c:108: INFO: Test #2: append to file
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9)
 copy_file_range02.c:108: INFO: Test #3: closed file descriptor
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9)
 copy_file_range02.c:108: INFO: Test #4: invalid flags
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #5: immutable file
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EPERM (1)
 copy_file_range02.c:108: INFO: Test #6: swap file
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: ETXTBSY (26)
 copy_file_range02.c:108: INFO: Test #7: overlaping range
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #8: block device
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #9: char device
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #10: fifo
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #11: pipe
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #12: max length lenght
 copy_file_range02.c:141: FAIL: copy_file_range failed unexpectedly; expected EOVERFLOW, but got: EFBIG (27)
 copy_file_range02.c:108: INFO: Test #13: max file size
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EFBIG (27)
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 copy_file_range.h:39: INFO: Testing __NR_copy_file_range syscall
 tst_device.c:87: INFO: Found free device 1 '/dev/loop1'
 Setting up swapspace version 1, size = 36 KiB (36864 bytes)
 no label, UUID=7ef630e1-d0f3-4072-91ec-ae49ab13c6dc
 copy_file_range02.c:108: INFO: Test #0: readonly file
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9)
 copy_file_range02.c:108: INFO: Test #1: directory
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EISDIR (21)
 copy_file_range02.c:108: INFO: Test #2: append to file
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9)
 copy_file_range02.c:108: INFO: Test #3: closed file descriptor
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9)
 copy_file_range02.c:108: INFO: Test #4: invalid flags
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #5: immutable file
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EPERM (1)
 copy_file_range02.c:108: INFO: Test #6: swap file
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: ETXTBSY (26)
 copy_file_range02.c:108: INFO: Test #7: overlaping range
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #8: block device
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #9: char device
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #10: fifo
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #11: pipe
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
 copy_file_range02.c:108: INFO: Test #12: max length lenght
 copy_file_range02.c:141: FAIL: copy_file_range failed unexpectedly; expected EOVERFLOW, but got: EFBIG (27)
 copy_file_range02.c:108: INFO: Test #13: max file size
 copy_file_range02.c:137: PASS: copy_file_range failed as expected: EFBIG (27)

 Summary:
 passed 26
 failed 2
 skipped 0
 warnings 0
 tag=copy_file_range02 stime=1573118536 dur=1 exit=exited stat=1 core=no cu=2 cs=7

Po-Hsu Lin (cypressyew) on 2019-11-07
tags: added: 5.3 bionic i386 sru-20191021 ubuntu-ltp-syscalls

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1851653

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Po-Hsu Lin (cypressyew) on 2019-11-29
tags: added: sru-20191111

copy_file_range changed behavior on 5.3, which would cause such failures.

LTP changes to accomodate that were committed on September 30th and October 29th, though.

Maybe this could be caused by the combination of linux 5.3, glibc 2.27 and whatever ltp version was used. Do we track the ltp commit id that was tested somehow?

Cascardo.

Po-Hsu Lin (cypressyew) wrote :

Sadly no.

I have a bug to print commit SHA1 filed https://bugs.launchpad.net/bugs/1855057
Will work on that to ensure we have a more traceable test history.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers