[LTP] [PATCH v2] swapon04: Report TCONF when SELinux denies loop device I/O

Wake Liu wakel@google.com
Fri Oct 30 08:21:44 CET 2026


Hi Andrea,

On Wed, Oct 21, 2026 at 09:31:52AM +0000, Andrea Cervesato wrote:
> But did you check if other tests are having the same issue?

Yes. Only loop devices backed by a file on the freshly formatted test
filesystem are affected, since those files have no SELinux label, and
swapon04 is the only test that does that.

The other loop users (ioctl_loop*, ioctl09, uevent01, sys_block_loop01,
isofs.sh and quota_remount_test01.sh) keep their images in TMPDIR, like
the test device itself, and Android's policy allows the kernel domain
to access files there. Swap files on the test filesystem are fine too,
since swap I/O does not go through vfs_iter_{read,write}().

Thanks,
Wake

On Wed, Oct 21, 2026 at 5:31 PM Andrea Cervesato
<andrea.cervesato@suse.com> wrote:
>
> Hi Wake,
>
> unfortunately I don't see other options available but skipping the test
> "guessing" that SELinux enforcement is producing an EIO error.
>
> But did you check if other tests are having the same issue?
>
> Regards,
> --
> Andrea Cervesato
> SUSE QE Automation Engineer Linux
> andrea.cervesato@suse.com



-- 
Best Regards,
Wake Liu


More information about the ltp mailing list