On Fri, Oct 19, 2018 at 12:59:08PM -0300, Rafael Tinoco wrote:
Summary
kernel: 4.19.0-rc8 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git branch: master git commit: 91b15613ce7fb3e724ca0d433eef8e6bf15322af git describe: v4.19-rc8-95-g91b15613ce7f Test details: https://qa-reports.linaro.org/lkft/linux-mainline-oe-sanity/build/v4.19-rc8-...
Regressions (compared to build v4.19-rc8-40-g2a9666105445)
i386: ltp-quickhit-tests: * fsync01
* test src: git://github.com/linux-test-project/ltp.gitFor now, it does NOT look something serious: /dev/loop0 device wasn't released when iterating between different file-systems when testing fsync (worked for ext2 and ext3). It seems to be a LTP bug, I'm confirming.
Error:
mke2fs 1.43.5 (04-Aug-2017)/dev/loop0 is apparently in use by the system; will not make a filesystem here! tst_mkfs.c:94: BROK: mkfs.ext4:1: tst_test.c failed with 729
I'll double check and reply here.
Tested 50 iterations with same test, each test with ext2/ext3/ext4, using latest LTP, and was not able to reproduce this issue:
Opened the following BUG: https://bugs.linaro.org/show_bug.cgi?id=4029 to track LTP fix on our side and upstream project.
Nothing to worry on your side.
Wonderful, thanks for following up on this and letting me know.
greg k-h