Messages in this thread | | | Date | Wed, 27 Jul 2011 11:30:15 -0400 | From | Konrad Rzeszutek Wilk <> | Subject | Re: [PATCH 0/5] Collected vdso/vsyscall fixes for 3.1 |
| |
> > Anyhow, removed the benchmark code and ran it on 64-bit: > > > > sh-4.1# /test_vsyscall test > > Testing gettimeofday... > > [ 109.552261] test_vsyscall[2462] trap invalid opcode ip:400c8d sp:7fff84fab470 error:0 in test_vsyscall[400000+2000] > > Illegal instruction > > sh-4.1# /test_vsyscall intcc > > About to execute int 0xcc from RIP = 400959 > > [ 114.137150] test_vsyscall[2463] illegal int 0xcc (exploit attempt?) ip:400959 cs:e033 sp:7fff8b328310 ax:2c si:0 di:7fff8b3280f0 > > Caught SIGSEGV: Segmentation fault (Signal sent by the kernel [(nil)])RIP = 400959 > > > > [This is on git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git #testing, which > > has todays linus/master and your patchset] > > > > I'll set up Xen. Something's clearly still buggy.
You sure? This is what I get when I boot baremetal:
sh-4.1# sh-4.1# xen-detect Not running on Xen. sh-4.1# /test_vsyscall test Testing gettimeo[ 84.442819] test_vsyscall[3175] trap invalid opcode ip:400c8d sp:7fffa8a72dc0 error:0fday... in test_vsyscall[400000+2000] Illegal instruction sh-4.1# /test_vsyscall intcc About to execute[ 87.549820] test_vsyscall[3176] illegal int 0xcc (exploit attempt?) ip:400959 cs:33 sp:7fff0ccddff0 ax:2c s^G^G^G^G^G^G^Gsh-4.1# sh-4.1# /test_vsyscall intcc About to execute[ 90.283817] test_vsyscall[3177] illegal int 0xcc (exploit attempt?) ip:400959 cs:33 sp:7fffae8a8b40 ax:2c son fault (Signal sent by the kernel [(nil)])RIP = 400959
Unless the whole paravirt kernel is buggy. Hadn't tried to boot non-paravirt. -- 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/
| |