[LTP] using LTP to test read-only bind mounts

[George K. <gk...@au...>]

There has been an offline discussion about using LTP to test read-only
bind mounts; however, the tests will likely "fail" and not give good
results.  I would like to suggest that the LTP filesystem tests may need
to be enhanced to handle the read-only scenario.  For example, if the
filesystem tests were run on a read-write filesystem, then they should
return "pass"; however, if they were run on a read-only filesystem, then
they should return "untested" because it could not write to the
filesystem. In POSIX testing an "untested" result is considered a pass.

Pass: a test result belonging to this group is considered to be a pass
for compliance testing purposes: Pass, Warning, FIP, Unsupported, Not In
Use, Untested

Fail: a test result belonging to this group is considered to be a fail
for compliance testing purposes (unless the failure has been waived by
an agreed Problem Report in the Certification Problem Reporting
database): Fail, Uninitiated, Unresolved, Unreported

If one wants to stick with LTP's return codes, then we should use TWARN
found in /opt/ltp/include/test.h instead of UNTESTED.

Does anyone have an objection to making LTP's filesystem tests robust
enough to handle the read-only bind mount scenario?

-- 
George (gk4)