today i thought to myself "gosh. i can't think of a way to write a POSIX overlay filesystem that doesn't produce absolutely horrifyingly nonsensical inode semantics"
thinking that perhaps, i might just be very dumb, i opened the overlayfs documentation page
it turns out that the answer is "they are indeed", and the documentation claims this is alright because "many applications and tools ignore these values and will not be affected", which somehow fails to soothe me