Note that similar to the older gcc and upstream sanitizer bugs, this problem may be caused by some kernel API now returning a slightly different result, so it could be debatable whether the issue should be fixed in ThreadSanitizer, or in the kernel itself.
Note that similar to the older gcc and upstream sanitizer bugs, this problem may be caused by some kernel API now returning a slightly different result, so it could be debatable whether the issue should be fixed in ThreadSanitizer, or in the kernel itself.