Bit of a wild guess/hope that someone might know what this is. I'm
getting a strange error from valgrind about an ioctl that I'm definitely
not calling directly and I've got no idea why it would be trying to do
anything with a cdrom.
https://github.com/torvalds/linux/blob/master/include/uapi/linux/cdrom.h
(This logging about cannot open /etc/fstab is expected, it's running a
test in a sandbox)
DUMP: Can't open /etc/fstab for dump table information: No such file or
directory
DUMP: Date of this level 0 dump: Mon Mar 24 21:58:23 2025
DUMP: Dumping /dev/loop1 (/tmp/tmp.CguPpyLyWD/tmp.MLZ9IgD8cb) to
/tmp/tmp.CguPpyLyWD/tmp.1oLCTpg9jr
==4710== Warning: noted but unhandled ioctl 0x5395 with no size/direction hints.
==4710== This could cause spurious value errors to appear.
==4710== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a
proper wrapper.
The only ioctls I'm using are MTIOCPOS, MTIOCGET, BLKFLSBUF, MTIOCTOP
Otherwise I guess I'm going to have to try to find it in the debugger
(or just ignore it completely)
