New comment by ologantr on void-packages repository

https://github.com/void-linux/void-packages/issues/36447#issuecomment-1085620221

Comment:
This is probably caused by a recent commit on linux mainline, [aa6f8dcbab](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/kernel/dma/swiotlb.c?id=aa6f8dcbab473f3a3c7454b74caa46d36cdc5d13), 
that ended up being reverted because of some driver breakage (including ath9k): [bddac7c1e0](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/kernel/dma/swiotlb.c?id=bddac7c1e02ba47f0570e494c9289acea3062cc1).
The commit that caused this ended up in linux-stable 5.15.29 [2c1f97af38](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=2c1f97af38be151527380796d31d3c9adb054bf9),
and is now scheduled for removal on 5.15.33 [patch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.15/revert-swiotlb-rework-fix-info-leak-with-dma_from_device.patch).
For now you can go back to a linux version < 5.15.29 or wait for 5.15.33.