sync_file_range02 in ubuntu_ltp_syscalls fails

Bug #1819116 reported by Po-Hsu Lin on 2019-03-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned
Bionic
Undecided
Unassigned
Cosmic
Undecided
Unassigned
Disco
Undecided
Unassigned
Eoan
Undecided
Unassigned
linux-aws (Ubuntu)
Undecided
Unassigned
Bionic
Undecided
Unassigned
Cosmic
Undecided
Unassigned
Disco
Undecided
Unassigned
Eoan
Undecided
Unassigned
linux-azure (Ubuntu)
Undecided
Unassigned
Bionic
Undecided
Unassigned
Cosmic
Undecided
Unassigned
Disco
Undecided
Unassigned
Eoan
Undecided
Unassigned
linux-gke (Ubuntu)
Undecided
Unassigned
Bionic
Undecided
Unassigned
Eoan
Undecided
Unassigned

Bug Description

syslog output attached as attachment.

<<<test_output>>>
incrementing stop
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
tst_supported_fs_types.c:72: INFO: Kernel supports ext2
tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
tst_supported_fs_types.c:72: INFO: Kernel supports ext3
tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
tst_supported_fs_types.c:72: INFO: Kernel supports ext4
tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
tst_supported_fs_types.c:72: INFO: Kernel supports xfs
tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist
tst_supported_fs_types.c:72: INFO: Kernel supports vfat
tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
tst_test.c:1157: INFO: Testing on ext2
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
mke2fs 1.44.6 (5-Mar-2019)
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
sync_file_range02.c:54: PASS: Test file range synced to device
tst_test.c:1157: INFO: Testing on ext3
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts=''
mke2fs 1.44.6 (5-Mar-2019)
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
sync_file_range02.c:54: PASS: Test file range synced to device
tst_test.c:1157: INFO: Testing on ext4
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
mke2fs 1.44.6 (5-Mar-2019)
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
sync_file_range02.c:54: PASS: Test file range synced to device
tst_test.c:1157: INFO: Testing on xfs
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts=''
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
sync_file_range02.c:54: PASS: Test file range synced to device
tst_test.c:1157: INFO: Testing on btrfs
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts=''
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
sync_file_range02.c:54: PASS: Test file range synced to device
tst_test.c:1157: INFO: Testing on vfat
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts=''
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
sync_file_range02.c:54: PASS: Test file range synced to device
tst_test.c:1157: INFO: Testing on ntfs
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts=''
The partition start sector was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0.
The number of sectors per track was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0.
The number of heads was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0.
To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set.
Windows will not be able to boot from this device.
safe_macros.c:739: INFO: Trying FUSE...
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
sync_file_range02.c:56: FAIL: Synced 0, expected 33554432

Summary:
passed 6
failed 1
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=11 termination_type=exited termination_id=1 corefile=no
cutime=10 cstime=157
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: 20190115

       ###############################################################

            Done executing testcases.
            LTP Version: 20190115
       ###############################################################

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-7-generic 5.0.0-7.8
ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Mar 8 06:01 seq
 crw-rw---- 1 root audio 116, 33 Mar 8 06:01 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:

Date: Fri Mar 8 07:02:13 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:

ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,1152008n1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-7-generic N/A
 linux-backports-modules-5.0.0-7-generic N/A
 linux-firmware 1.177
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU

Po-Hsu Lin (cypressyew) wrote :

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 1819116

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

Need to check if we can reproduce this on older kernel.
This is a new test case that just landed on Feb.21

Po-Hsu Lin (cypressyew) wrote :

Yes this issue can be found on other releases as well (B/C)

Sean Feole (sfeole) wrote :

affects disco 5.0.0-1007.7-aws amd64 & arm64

tags: added: arm64
Sean Feole (sfeole) wrote :

affects cosmic 4.18.0-1017.19-aws amd64 & arm64

tags: added: cosmic
summary: - sync_file_range02 in ubuntu_ltp_syscalls failed on D
+ sync_file_range02 in ubuntu_ltp_syscalls fails C/D

affects disco, 5.0.0-1007.7 linux-azure

Sean Feole (sfeole) wrote :

affects bionic, 4.15.0-1040.42 linux-aws

summary: - sync_file_range02 in ubuntu_ltp_syscalls fails C/D
+ sync_file_range02 in ubuntu_ltp_syscalls fails
tags: added: aws bionic
Sean Feole (sfeole) wrote :

affects bionic linux-gke 4.15.0-1033.35

no longer affects: linux-gke (Ubuntu Cosmic)
no longer affects: linux-gke (Ubuntu Disco)
Sean Feole (sfeole) wrote :

affects linux-oem-osp1 5.0.0-1008.9

Sean Feole (sfeole) wrote :

This also affects Eoan 5.2.0-4.5-generic, on bare-metal or the AWS cloud.

tags: added: eoan linux-generic sru-20190603
Sean Feole (sfeole) wrote :
Po-Hsu Lin (cypressyew) on 2019-06-24
tags: added: linux-kvm ubuntu-ltp-syscalls
Po-Hsu Lin (cypressyew) wrote :

Failed on D-AWS (t3.medium), this failure was not spotted across all instances

Test failed with vfat.:
tst_mkfs.c:90: INFO: Formatting /dev/loop3 with vfat opts='' extra opts=''
sync_file_range02.c:111: INFO: Pre-filling file
sync_file_range02.c:71: PASS: Sync equals write
sync_file_range02.c:74: FAIL: Sync inside of write: Synced 27854336, expected 16777216
sync_file_range02.c:71: PASS: Sync overlaps with write

Changed in linux (Ubuntu Eoan):
assignee: nobody → Kai-Heng Feng (kaihengfeng)
Kai-Heng Feng (kaihengfeng) wrote :

Seems like the issue can't be reproduced on Disco anymore:
Summary:
passed 18
failed 0
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=6 termination_type=exited termination_id=0 corefile=no
cutime=4 cstime=79
<<<test_end>>>
INFO: ltp-pan reported all tests PASS
LTP Version: 20190517

Changed in linux (Ubuntu Eoan):
assignee: Kai-Heng Feng (kaihengfeng) → nobody
Sean Feole (sfeole) on 2019-09-26
tags: added: sru-20190902
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers