There is a similar bug report [1] for NFS, and the fix has already landed in Bionic kernel [2]
It's not the same issue as the copy_range works except the "beyond" copy test here. [1] https://www.spinics.net/lists/linux-nfs/msg63817.html [2] 6d3b5d8d8dd1c14f991ccab84b40f8425f1ae91b in Bionic tree -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755999 Title: Reproducible hang in ext4 generic/430 with xfstest from upstream Status in linux package in Ubuntu: Confirmed Bug description: While testing the latest xfstest from upstream, the generic/430 test will hang with ext4 test. It looks like this issue was caused by the following command to copy beyond the file: /usr/sbin/xfs_io -i -f -c "copy_range -s 4000 -l 2000 /home/ubuntu/test/test-430/file" "/home/ubuntu/test/test-430/beyond" The copied file will have a correct MD5 as expected. e68d4a150c4e42f4f9ea3ffe4c9cf4ed beyond But the command will never return. The file size of test-430/file is 5000, so a copy_range call with source offset 4000 with length 1000 works, but > 1000 does not. Steps: 1. Deploy a node with Bionic (should have a /dev/sdb available for the test) 2. Run: sudo apt-get install git python-minimal -y git clone --depth=1 https://github.com/Cypresslin/autotest-client-tests.git -b kteam-xfstest-upstream git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests 3. Run the test with the following command: AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ (The test suite can be built manually, but it's easier to do this with autotest framework) To run this test solely after the test partition has been creation on /dev/sdb: mkdir /home/ubuntu/test cd autotest/client/tmp/xfstests/src/xfstests-bld/xfstests-dev sudo su export TEST_DIR=/home/ubuntu/test export TEST_DEV=/dev/sdb1 ./check generic/430 Tested with the latest mainline kernel, 4.16.0-041600rc5-generic, and the bug still exist. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: boot/vmlinuz-4.15.0-10-generic] ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1148 F.... pulseaudio /dev/snd/controlC1: ubuntu 1148 F.... pulseaudio Date: Thu Mar 15 14:24:46 2018 InstallationDate: Installed on 2018-03-15 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d1980d27-9063-4d92-aa10-1fb240453d8d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/14/2014:svnDellInc.:pnDellPrecisionM3800:pvrA07:rvnDellInc.:rnDellPrecisionM3800:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
