diff options
| author | Benjamin Berg <benjamin.berg@intel.com> | 2024-07-03 15:45:33 +0200 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2024-07-03 17:09:49 +0200 |
| commit | 5168f6b4a4d8fb5f731f2107924f72dffeae84fc (patch) | |
| tree | 5b3f6caa14658ba1956d57eae0a92b4606a3950f /arch/um/kernel/exec.c | |
| parent | um: Delay flushing syscalls until the thread is restarted (diff) | |
| download | linux-5168f6b4a4d8fb5f731f2107924f72dffeae84fc.tar.gz linux-5168f6b4a4d8fb5f731f2107924f72dffeae84fc.zip | |
um: Do not flush MM in flush_thread
There should be no need to flush the memory in flush_thread. Doing this
likely worked around some issue where memory was still incorrectly
mapped when creating or cloning an MM.
With the removal of the special clone path, that isn't relevant anymore.
However, add the flush into MM initialization so that any new userspace
MM is guaranteed to be clean.
Signed-off-by: Benjamin Berg <benjamin.berg@intel.com>
Link: https://patch.msgid.link/20240703134536.1161108-10-benjamin@sipsolutions.net
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'arch/um/kernel/exec.c')
| -rw-r--r-- | arch/um/kernel/exec.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/arch/um/kernel/exec.c b/arch/um/kernel/exec.c index 5c8836b012e9..2c15bb2c104c 100644 --- a/arch/um/kernel/exec.c +++ b/arch/um/kernel/exec.c @@ -24,11 +24,6 @@ void flush_thread(void) { arch_flush_thread(¤t->thread.arch); - unmap(¤t->mm->context.id, 0, TASK_SIZE); - if (syscall_stub_flush(¤t->mm->context.id) < 0) { - printk(KERN_ERR "%s - clearing address space failed", __func__); - force_sig(SIGKILL); - } get_safe_registers(current_pt_regs()->regs.gp, current_pt_regs()->regs.fp); |