Hi Huang and Chao.
I feel like this special loopback handling alongside Chao's
14197d546b93 on f2fs-tools is just unnecessarily complicating the code
flow.
We're now doing what, lookup to /sys, parse original backing file,
remove trailing newline char, stat()'ing it to make sure it exists?
What
Currently mkfs/fsck gets the following error when executed by
non-root users:
Info: open /dev/loop0 failed errno:13
Error: Not available on mounted device!
Let's fix it by reading the backing file from sysfs.
Fixes: 14197d546b93 ("f2fs-tools: fix to check loop device")
Signed-off-by: