--- Comment #21 from Sumit Bose <sbose(a)redhat.com> ---
I run couple of tests and was able to reproduce similar crashes with SIGBUS
only on files which were shortened with e.g. the truncate command. I'm not sure
if it is worth to try to protect the memory mapped files against this. I'm also
not sure how. Calling fstat() before every memory access will slow things down
considerably. Maybe sssd_nss can set an inotify watch to detect such a change
but there would still be a chance the the truncation happens while sssd_nss is
working in the files before handling inotify.
The most promising protection I found is F_SEAL_SHRINK, see man fcntl for
details, but this requires an anonymous file in tmpfs, see man memfd_create for
You are receiving this mail because:
You are on the CC list for the bug.