This extends the set in r316028 to allow all tests to pass or be skipped
on a system without cd9660 support.
Obtained from: CheriBSD
Sponsored by: DARPA, AFRL
MFC After: 1 week
Differential D10516
Check to see if the kernel has cd9660 before attempting to mount created images brooks on Apr 26 2017, 11:39 PM. Authored by Tags None Referenced Files
Subscribers
Details This extends the set in r316028 to allow all tests to pass or be skipped Obtained from: CheriBSD tested on a mips64 qemu system without cd9660 support
Diff Detail
Event TimelineComment Actions Real in that the MALTA64 kernel doesn't contain a cd9660. r316028 seems to have only covered half the cases that require mounting the created filesystem. Comment Actions I'm ok with all of the changes but to :o_flag_isolevel_3 (it would eliminate potential coverage today)
Comment Actions FWIW, I'm not convinced mounting the file systems is the best option. We should probably mount one of them, but extracting the files with tar would be more portable.
Comment Actions After realizing I misunderstood how atf-sh works (atf-check returns immediate failure if it fails, not at script exit), I wonder if check_cd9660_support should be rolled into mount_image. Then we'll do unvalidated image creation testing even when kernel support is missing. Comment Actions Hmm, it can't actually go in mount_image. I'll revise this diff and move all the check_cd9660_support calls down. Comment Actions I'll open another review to use tar instead of mount_cd9660. I think your input is correct there. |