从 exec 系统调用返回时使用 iret

Question

我注意到在 start_thread 函数的末尾，它是在 exec 的大部分工作完成后调用的，有一个对 force_iret 的调用：

    static void
    start_thread_common(struct pt_regs *regs, unsigned long new_ip,
        unsigned long new_sp,
        unsigned int _cs, unsigned int _ss, unsigned int _ds)
    {
         loadsegment(fs, 0);
         loadsegment(es, _ds);
         loadsegment(ds, _ds);
         load_gs_index(0);
         regs->ip       = new_ip;
         regs->sp       = new_sp;
         regs->cs       = _cs;
         regs->ss       = _ss;
         regs->flags        = X86_EFLAGS_IF;
         force_iret();
    }

我认为这样做是为了确保 sysexit 不习惯于 return 用户 space。那么为什么 iret 必须在 return 来自 exec 时使用？

Answer 1

此函数修改 sysret/sysexit 不会恢复的寄存器。

这里是arch/x86/include/asm/thread_info.h：

/*
 * Force syscall return via IRET by making it look as if there was
 * some work pending. IRET is our most capable (but slowest) syscall
 * return path, which is able to restore modified SS, CS and certain
 * EFLAGS values that other (fast) syscall return instructions
 * are not able to restore properly.
 */
#define force_iret() set_thread_flag(TIF_NOTIFY_RESUME)

从 exec 系统调用返回时使用 iret

Use of iret when returning from exec system call

c

linux

kernel

linux-kernel