Hi Krzysztof, On 2025-03-05 at 17:31:49 +0100, Krzysztof Niemiec wrote: > Don't we run into the same issue as in V1, meaning we use an unknown > current->active_mm (since we run in a kthread, and cannot control it) to > use as the current->mm? Maybe a better approach would be to create a new > mm for the duration of the test, similarly to how the patch Janusz > mentioned does it? (51104c19d857)
As per discussion with Chris, using active_mm is the correct way of enabling current->mm in kthread. On the other hand it may also expose issues with underlying tests because they didn't previously run on such hardware. I think potential fixes to those tests should be addressed in separate patch. Mikołaj
