20 Feb
2020
20 Feb
'20
1:30 p.m.
Hi John,
On Thu, 20 Feb 2020 at 08:45, John Bates jbates@chromium.org wrote:
The previous code was not thread safe and caused undefined behavior from spurious duplicate resource IDs. In this patch, an atomic_t is used instead. We no longer see any duplicate IDs in tests with this change.
Signed-off-by: John Bates jbates@chromium.org
Adding a fixes tag like below makes it easier to track. Especially for Greg and team who are working on stable kernels.
Fixes: 3e93bc2a58aa ("drm/virtio: make resource id workaround runtime switchable.")
HTH Emil