On Thu, 04 May 2023 14:55:24 +0200, Jan Kara wrote:
> When using cached extent stored in extent status tree in tree->cache_es
> another process holding ei->i_es_lock for reading can be racing with us
> setting new value of tree->cache_es. If the compiler would decide to
> refetch tree->cache_es at an unfortunate moment, it could result in a
> bogus in_range() check. Fix the possible race by using READ_ONCE() when
> using tree->cache_es only under ei->i_es_lock for reading.
>
> [...]
Applied, thanks!
[1/1] ext4: Fix data races when using cached status extents
commit: 185e33d15ebf4a9d779fa78249b6cc95a071967e
Best regards,
--
Theodore Ts'o <tytso@xxxxxxx>
