Description of problem: When posix xlator is compiled on a platform that doesn't support SEEK_DATA/SEEK_HOLE options for a seek operation, the brick process crashes when the client tries to use it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/20625 (posix: prevent crash when SEEK_DATA/HOLE is not supported) posted (#1) for review on master by Xavi Hernandez
COMMIT: https://review.gluster.org/20625 committed in master by "Shyamsundar Ranganathan" <srangana> with a commit message- posix: prevent crash when SEEK_DATA/HOLE is not supported Instead of not defining the 'seek' fop when it's not supported on the compilation platform, we simply return EINVAL when it's used. Fixes: bz#1611834 Change-Id: I253666d8910c5e2fffa3a3ba37085e5c1c058a8e Signed-off-by: Xavi Hernandez <xhernandez>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report. glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/
*** Bug 1658327 has been marked as a duplicate of this bug. ***