aboutsummaryrefslogtreecommitdiff
path: root/testsuite/id/id-g-works
diff options
context:
space:
mode:
authorDenys Vlasenko <vda.linux@googlemail.com>2020-12-09 20:56:43 +0100
committerDenys Vlasenko <vda.linux@googlemail.com>2020-12-09 20:56:43 +0100
commit56ee5765074b2f2389066f3234a4da21501d3eaa (patch)
treeb4fe1bbbd147350eaf90b688285cfb09ed07f3ab /testsuite/id/id-g-works
parente7d853b4eb080dd8ea6433d010378e119e5a4cb3 (diff)
downloadbusybox-56ee5765074b2f2389066f3234a4da21501d3eaa.tar.gz
mount: fix incorrect "success" exitcode if loop device setup fails
When mounting, in parallel, multiple loop devices (squashfs for the submitter's case), the following behavior can be observed: stat64(/path/to/image, {st_mode=S_IFREG|0644, st_size=4096, ...}) = 0 openat(AT_FDCWD, /path/to/image, O_RDWR|O_LARGEFILE) = 3 openat(AT_FDCWD, /dev/loop-control, O_RDWR|O_LARGEFILE|O_CLOEXEC) = 4 ioctl(4, LOOP_CTL_GET_FREE) = 12 close(4) = 0 openat(AT_FDCWD, /dev/loop12, O_RDWR|O_LARGEFILE) = 4 ioctl(4, LOOP_GET_STATUS64, {lo_offset=0, lo_number=12, lo_flags=LO_FLAGS_AUTOCLEAR, lo_file_name=/path/to/image, ...}) = 0 close(4) = 0 close(3) = 0 write(2, "mount: can't setup loop device\n", 31mount: can't setup loop device ) = 31 exit_group(0) = ? +++ exited with 0 +++ The ioctl LOOP_CTL_GET_FREE has resulted in the same result for a competing mount process. The subsequent ioctl LOOP_GET_STATUS64 fails, having succeeded for the competing mount process. Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'testsuite/id/id-g-works')
0 files changed, 0 insertions, 0 deletions