Input validation in mapped open functions
While working on #174, I played around with test_mapped_1.c
in order to determine constraints on the various function parameters (for write mode). Parameter sets outside the constraints seem to be able to trigger the following behaviors:
- reporting nondescript failure of the internal open and returning
sid = -1
- program abort after signal 11
- program abort after signal 6
- deadlock / infinite loop
- creating a file that causes
siondump
to abort after signal 11
It would be both more user-friendly and safe to perform thorough validation of the parameters, if the constraints turn out to be as simple as they appear to be.