Re: [PATCH x86/mm 6/6] x86-64 ia32 ptrace get/putreg32 current task

> But the ones that do the same thing for fs/es/ds are *not*. Those three 
> registers are kernel mode registers (ds/es are the regular kernel data 
> segment, fs is the per-cpu data segment), and restored on return to user 
> space from the stack.

Um, really?  This is x86-64 code.  AIUI those values don't have any effect
at all in 64-bit mode (as the kernel is).  I haven't found any code in
entry_64.S or ia32entry.S that touches them.  __switch_to uses direct
access to the segment registers just as I've done.


Thanks,
Roland
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH x86/mm 6/6] x86-64 ia32 ptrace get/putreg32 current task
  - From: Linus Torvalds <[email protected]>

References:
- [PATCH x86/mm 1/6] x86-64 ia32 ptrace pt_regs cleanup
  - From: Roland McGrath <[email protected]>
- [PATCH x86/mm 6/6] x86-64 ia32 ptrace get/putreg32 current task
  - From: Roland McGrath <[email protected]>
- Re: [PATCH x86/mm 6/6] x86-64 ia32 ptrace get/putreg32 current task
  - From: Chuck Ebbert <[email protected]>
- Re: [PATCH x86/mm 6/6] x86-64 ia32 ptrace get/putreg32 current task
  - From: Linus Torvalds <[email protected]>

Prev by Date: Re: Race between generic_forget_inode() and sync_sb_inodes()?
Next by Date: Re: [PATCH] Fix forgotten module release in xt_CONNMARK and xt_CONNSECMARK
Previous by thread: Re: [PATCH x86/mm 6/6] x86-64 ia32 ptrace get/putreg32 current task
Next by thread: Re: [PATCH x86/mm 6/6] x86-64 ia32 ptrace get/putreg32 current task
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]