Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1605872
| From | Cyrill Gorcunov <gorcunov@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [Q] Figuring out task mode |
| Date | 2017-03-21 19:10 +0100 |
| Message-ID | <tnwoj-6UG-35@gated-at.bofh.it> (permalink) |
| References | <tnvLz-6rG-3@gated-at.bofh.it> <tnvLz-6rG-1@gated-at.bofh.it> <tnw4V-6ys-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
/I renamed the mail's subject/ On Tue, Mar 21, 2017 at 10:45:57AM -0700, Andy Lutomirski wrote: > >> + task_pt_regs(current)->orig_ax |= __X32_SYSCALL_BIT; > >> current->thread.status &= ~TS_COMPAT; > > > > Hi! I must admit I didn't follow close the overall series (so can't > > comment much here :) but I have a slightly unrelated question -- is > > there a way to figure out if task is running in x32 mode say with > > some ptrace or procfs sign? > > You should be able to figure out of a *syscall* is x32 by simply > looking at bit 30 in the syscall number. (This is unlike i386, which > is currently not reflected in ptrace.) Yes, syscall number will help but from criu perpspective (until Dima's patches are merged into mainlie) we need to figure out if we can dump x32 tasks without running parasite code inside, ie via plain ptrace call or some procfs output. But looks like it's impossible for now. > Do we actually have an x32 per-task mode at all? If so, maybe we can > just remove it on top of Dmitry's series. Don't think so, x32 should be set upon exec and without Dima's series it is immutable I think.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Cyrill Gorcunov <gorcunov@gmail.com> - 2017-03-21 18:30 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Andy Lutomirski <luto@amacapital.net> - 2017-03-21 18:50 +0100
[Q] Figuring out task mode Cyrill Gorcunov <gorcunov@gmail.com> - 2017-03-21 19:10 +0100
Re: [Q] Figuring out task mode Andy Lutomirski <luto@amacapital.net> - 2017-03-22 01:00 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Cyrill Gorcunov <gorcunov@gmail.com> - 2017-03-21 19:50 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() hpa@zytor.com - 2017-03-21 20:00 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Cyrill Gorcunov <gorcunov@gmail.com> - 2017-03-21 20:20 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() hpa@zytor.com - 2017-03-21 20:30 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Cyrill Gorcunov <gorcunov@gmail.com> - 2017-03-21 20:30 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() hpa@zytor.com - 2017-03-21 20:00 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Andy Lutomirski <luto@amacapital.net> - 2017-03-21 20:40 +0100
Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Cyrill Gorcunov <gorcunov@gmail.com> - 2017-03-21 20:40 +0100
csiph-web