Comment 5 for bug 1915095

I am no longer able to reproduce this behavior, neither on Ubuntu 18.04 nor 20.04. I double-checked that I had both filesystems mounted with strictatime: the atime was updated when I ran `cat test`.

This is baffling because it was definitely a problem before, and I don't see references anywhere in the source code nor the patches to case-insensitive "atime". I'm not sure how, but it now appears to me to be fixed.