On Fri 24-03-23 09:43:10, Joel Fernandes wrote: [...] > Michal, would you also mind providing the full stack you are seeing > just so we know it is the same issue (i.e. triggered via exec)? Yes, it is the exec path [ 544.236782][T20518] Call Trace: [ 544.237467][T20518] <TASK> [ 544.238034][T20518] move_page_tables+0x8e4/0x930 [ 544.238039][T20518] shift_arg_pages+0xb5/0x180 [ 544.238044][T20518] ? mprotect_fixup+0x1ce/0x2e0 [ 544.238046][T20518] setup_arg_pages+0x256/0x2b0 [ 544.238049][T20518] load_elf_binary+0x375/0x15d0 [ 544.238052][T20518] ? __kernel_read+0x2e8/0x310 [ 544.238056][T20518] ? __kernel_read+0x2e8/0x310 [ 544.238059][T20518] bprm_execve+0x2ec/0x650 [ 544.238062][T20518] do_execveat_common.isra.42+0x1ed/0x230 [ 544.238064][T20518] __x64_sys_execve+0x32/0x40 [ 544.238067][T20518] do_syscall_64+0x5b/0x80 [ 544.238072][T20518] ? __SCT__preempt_schedule_notrace+0x8/0x8 [ 544.238075][T20518] ? __SCT__preempt_schedule_notrace+0x8/0x8 [ 544.238076][T20518] ? exit_to_user_mode_prepare+0xfc/0x230 [ 544.250270][T20518] ? syscall_exit_to_user_mode+0x18/0x40 [ 544.250292][T20518] ? do_syscall_64+0x67/0x80 [ 544.250294][T20518] ? exc_page_fault+0x67/0x150 [ 544.250297][T20518] entry_SYSCALL_64_after_hwframe+0x61/0xcb -- Michal Hocko SUSE Labs