Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1196155
| From | Paolo Bonzini <pbonzini@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Dealing with the NMI mess |
| Date | 2015-07-30 18:00 +0200 |
| Message-ID | <pRYps-2RD-23@gated-at.bofh.it> (permalink) |
| References | (7 earlier) <pPwQG-30s-17@gated-at.bofh.it> <pPGmZ-8tY-7@gated-at.bofh.it> <pPNou-1ET-13@gated-at.bofh.it> <pPONA-3O6-7@gated-at.bofh.it> <pPOXg-3Zq-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 24/07/2015 19:20, Andy Lutomirski wrote: > > Andy, section 5.8 of the SDM makes me think we could possibly abuse SYSRET > > to emulate IRET, and then possibly simplify the flags processing. It says > > that it takes the CPL3 code segment but nowhere it says that the target is > > validated for effectively being userland, and further it suggests that it > > doesn't validate anything : > > > > "It is the responsibility of the OS to ensure the descriptors in > > the GDT/LDT correspond to the selectors loaded by SYSCALL/SYSRET > > (consistent with the base, limit, and attribute values forced by > > the instructions)." > You are an evil bastard. I seriously doubt that this will work. > SYSRET goes to CPL3 no matter what. Also, I don't think you want to > start poking at MSRs to return. On Intel the bottom two bits of the selector are forced to 11. The pseudocode of SYSRET in the SDM has an explicit CS.Selector ← (IA32_STAR[63:48]+ either 0 or 16) OR 3; ... SS.Selector ← (IA32_STAR[63:48]+8) OR 3; On AMD it's even worse, because you get a weird state with CS.DPL=CS.RPL=SS.DPL=SS.RPL=0 but still the CPL is 3. This is seriously messed up because the CPL is always SS.DPL except in this case. AMD even had to add a separate field for the CPL to their VM control block, just to account for this case. Intel more sanely uses SS.DPL. Paolo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Dealing with the NMI mess Steven Rostedt <rostedt@goodmis.org> - 2015-07-23 23:40 +0200
Re: Dealing with the NMI mess Linus Torvalds <torvalds@linux-foundation.org> - 2015-07-23 23:50 +0200
Re: Dealing with the NMI mess Andy Lutomirski <luto@amacapital.net> - 2015-07-24 00:00 +0200
Re: Dealing with the NMI mess Linus Torvalds <torvalds@linux-foundation.org> - 2015-07-24 00:10 +0200
Re: Dealing with the NMI mess Peter Zijlstra <peterz@infradead.org> - 2015-07-24 10:20 +0200
Re: Dealing with the NMI mess Willy Tarreau <w@1wt.eu> - 2015-07-24 11:10 +0200
Re: Dealing with the NMI mess Steven Rostedt <rostedt@goodmis.org> - 2015-07-24 14:00 +0200
Re: Dealing with the NMI mess Peter Zijlstra <peterz@infradead.org> - 2015-07-24 14:50 +0200
Re: Dealing with the NMI mess Steven Rostedt <rostedt@goodmis.org> - 2015-07-24 15:10 +0200
Re: Dealing with the NMI mess Willy Tarreau <w@1wt.eu> - 2015-07-24 15:30 +0200
Re: Dealing with the NMI mess Peter Zijlstra <peterz@infradead.org> - 2015-07-24 15:40 +0200
Re: Dealing with the NMI mess Peter Zijlstra <peterz@infradead.org> - 2015-07-24 15:40 +0200
Re: Dealing with the NMI mess Paolo Bonzini <pbonzini@redhat.com> - 2015-07-30 17:50 +0200
Re: Dealing with the NMI mess Borislav Petkov <bp@alien8.de> - 2015-07-31 06:30 +0200
Re: Dealing with the NMI mess Paolo Bonzini <pbonzini@redhat.com> - 2015-07-30 18:00 +0200
Re: Dealing with the NMI mess Andy Lutomirski <luto@amacapital.net> - 2015-07-23 23:50 +0200
Re: Dealing with the NMI mess Willy Tarreau <w@1wt.eu> - 2015-07-24 00:00 +0200
Re: Dealing with the NMI mess Willy Tarreau <w@1wt.eu> - 2015-07-23 23:50 +0200
csiph-web