KASAN uses annotations (see include/linux/instrumented.h) for atomic operations instead of compiler instrumentation. It makes sense to add tests to check that KASAN can detect bad atomic accesses.
FYI, I'm looking into this.