When fread causes a segmentation fault, I would suspect incompatible code, such as a mismatch of shared library versions. Since the segmentation fault when accessing a locked file is definitely not an intended feature, I have strong doubts that you will find anything in the release notes about this.
Another possibility is that the program in question doesn't use fread correctly. Perhaps the earlier kernel was more lenient and accepted incorrect usage, whereas the new kernel doesn't. In my opinion, this is less likely.
Note that fread is not a system call, although it may use the read system call. Does the same problem occur with read?
Last edited by berndbausch; 11-24-2020 at 09:32 PM.
|