On 5/11/25 9:23 PM, Johannes Berg wrote:
On Fri, 2025-05-09 at 11:50 +0200, Christian Lamparter wrote:
What's interesting/very strange strange about this time-travel stuff:
commit 0b8b2668f998 ("um: insert scheduler ticks when userspace does not yield")
$ git descri
nted: "I think it is better to just not backport
commit 0b8b2668f998 ("um: insert scheduler ticks when userspace does not yield")
"
Link:
https://lore.kernel.org/linux-um/8ce0b6056a9726e540f61bce77311278654219eb.ca...@sipsolutions.net/
Cc: # 6.12.y
Cc: Benjamin Berg
Signed-off
is it possible to backport 0b8b2668f9981c1fefc2ef892bd915288ef01f33 too?
Or is it better to revert 887c5c12e80c8424bd471122d2e8b6b462e12874 again
in the stable releases?
Best Regards,
Christian Lamparter
---
I suspect it is this code in ASAN that uses sched_yield
https://github.com/llvm/l
tty0 there.
CC: Thomas Meyer
Fixes: d7ffac33631b ("um: stdio_console: Make preferred console")
Signed-off-by: Christian Lamparter
---
arch/um/kernel/um_arch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/um/kernel/um_arch.c b/arch/um/kernel/um_arch.c
el command line parameters "mem=64M", will be
passed to user space.
That's why, I think it would be nicer, if this is working out
of the box again :).
Signed-off-by: Christian Lamparter
---
arch/um/kernel/um_arch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
