tree 1ed84dab9e844cb3bb7f81f0edd9eeb6b20030b1
parent 8f82c027c8969d965c43909da639e7790af19956
author Kunqiu Chen <camsyn@foxmail.com> 1750321551 +0800
committer GitHub <noreply@github.com> 1750321551 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJoU8mQCRC1aQ7uu5UhlAAAO3AQAAfJzsS7qYAth+CFDD2lDPpt
 2F3QYdK7QlgD30B59IdCCTJrZowvqYRB1cQudbxz7N1nCwCSWmmWzLqHROXrb9YO
 N0fbA3Dsi/XAFGAdT+ZrMFXMzzQjdI37qh1Q9M7Df6W0PONKdOWbkr9FBU4p8mFD
 Vtnqj15m/md2TV9YWN2OuBuw1Mj1ydE8dDD0YwMDCN/iofRTVShmxhKEulKNEzuj
 5FZwwgbUOTSckzUbAVdORHc9VJC42HgOwiU2H9XZV63SSH7bhlk1ed+2M4EExc0f
 bjSrHweexBNfQt3zF9+LOBj36WTg+9n36mkGzK0SgThIBTLDLr1aDSwbe/FY0pnW
 RpY8GNGWRSEinpxLnGXFSr89+oEJZ56YpVxYLxLdQmzzVywS+WiYsamZ9cVV9NqH
 GZMrCNjy4dPkrKExvU6egPOPWvSE+dKn4Miu1Mp0Vob+IfDBmQQjjWeORhLl1W7L
 7K5xDfAwaVJOioZRDd3pNJLKyckHtJrA0b3bqs/HjX40HNjR1b7kdW1VcEkvKXX6
 pysI4xa8G5cPo4Jg+KHFImRl9ChPvOXsrAD2pUOphQCjppETOhZCwTbSorr/eXLb
 CJpEYTRNKbzNJlCeJB9kdEwREl8d1BWUCd+pOph8oZFYq8XPA1oBbtUw0xQEKPpq
 ZvIuNdnjiUoexWIeeuYp
 =gRMu
 -----END PGP SIGNATURE-----
 

[TSan] Make Shadow/Meta region inclusive-exclusive (#144647)

This commit changes the interval shadow/meta address check from
inclusive-inclusive ( $[\mathrm{start}, \mathrm{end}]$ ) to
inclusive-exclusive ( $[\mathrm{start}, \mathrm{end})$ ), to resolve the
ambiguity of the end point address. This also aligns the logic with the
check for `isAppMem` (i.e., inclusive-exclusive), ensuring consistent
behavior across all memory classifications.

1. The `isShadowMem` and `isMetaMem` checks previously used an
inclusive-inclusive interval, i.e., $[\mathrm{start}, \mathrm{end}]$,
which could lead to a boundary address being incorrectly classified as
both Shadow and Meta memory, e.g., 0x3000_0000_0000 in
`Mapping48AddressSpace`.
- What's more, even when Shadow doesn't border Meta, `ShadowMem::end`
cannot be considered a legal shadow address, as TSan protects the gap,
i.e., `ProtectRange(ShadowEnd(), MetaShadowBeg());`

2. `ShadowMem`/`MetaMem` addresses are derived from `AppMem` using an
affine-like transformation (`* factor + bias`). This transformation
includes two extra modifications: high- and low-order bits are masked
out, and for Shadow Memory, an optional XOR operation may be applied to
prevent conflicts with certain AppMem regions.
- Given that all AppMem regions are defined as inclusive-exclusive
intervals, $[\mathrm{start}, \mathrm{end})$, the resulting Shadow/Meta
regions should logically also be inclusive-exclusive.

Note: This change is purely for improving code consistency and should
have no functional impact. In practice, the exact endpoint addresses of
the Shadow/Meta regions are generally not reached.