On Sat, Dec 10, 2022, at 1:08 AM, stsp wrote: > Hi. > > I am playing with 32bit compatibility segments, > and I am observing something very strange. > To demonstrate the problem, I did the change > to the kernel sigreturn test-case, and it is attached. > The change just moves the magic value to EAX > and calls an interrupt that produces a SIGSEGV. > The SIGSEGV handler prints the needed regs. > This patch intentionally adds 0x100000000 to > the RIP register, because AFAIK the high part > or 64bit regs are irrelevant in compatibility mode. > Now with high part of RIP non-zero, we see this: > $ ./sigreturn_64 > err=0 trapno=d ax=0 ip=100000003 > > OK, obviously our asm code didn't execute - > why is so? How does the high part of RIP > affect compatibility mode? > Then lets start the same example under gdb: > Program received signal SIGSEGV, Segmentation fault. > 0x0000000000403008 in int31 () > (gdb) > Continuing. > err=18a trapno=d ax=a5f3 ip=403008 > > Wow! Much better now: error code is correct, > ax is correct, but ip is invalid. I generally distrust gdb when mixed modes are involved -- it's fundamentally intensely buggy. Now maybe you're not hitting the bugs I know of, but still... Anyway, the behavior I expect (not that I've tested this, but based on my memory of how this is all supposed to work) is that an attempt to return to user mode will fail with #GP because the full value of RIP is compared to the segment limit, which is 2^32-1. And #GP is 0xd, so your non-gdb outputs look broadly correct...
