A fix for this bug is now staged as part of v5.4.132 to be included in a kernel update soon (it will be in a 5.11 update around the same time but not separately tracked there). For 5.13 it should already be included.
A fix for this bug is now staged as part of v5.4.132 to be included in a kernel update soon (it will be in a 5.11 update around the same time but not separately tracked there). For 5.13 it should already be included.