GlusterFS processes perform lgetxattr() system calls related to bit-rot detection even though it is disabled

Issue

While doing system call traces during normal file system activity, we found calls of the form:

lgetxattr("/path/to/brick/data/.glusterfs/12/34/1234......", "trusted.bit-rot.bad-file", ... )

This is unexpected because we have not enabled bit-rot detection on the volume, and features.bitrot is set to "disable":

# gluster volume get <volname> bitrot
Option                                  Value                                   
------                                  -----                                   
features.bitrot                         disable

Is there a solution that would eliminate these lgetxattr() calls?