Date: Tue, 26 Jun 2018 16:41:44 +0300 From: Vasily Averin <vvs@...tuozzo.com> To: Solar Designer <solar@...nwall.com> Cc: owl-dev@...ts.openwall.com Subject: Re: 32-bit syscall breakage in -431 kernel with KAISER On 2018-06-26 13:55, Solar Designer wrote: > On Tue, Jun 26, 2018 at 01:21:31PM +0300, Vasily Averin wrote: >> I've compiled 028stab123.1 kernel locally, >> installed it on my test node and found that it crashes on right on boot, >> during console init. > > We're not seeing behavior this bad. For us, only some 32-bit syscalls > against 64-bit kernel are affected. > > Chris Bopp on owl-users reported that for his rebuild with > CONFIG_KAISER=n "the host hung at boot". So maybe you didn't enable > KAISER in your build? No, my kernel have CONFIG_KAISER=Y Seems I have problem with dump/restore registers in some exception(irq?) handler. I observe EIP=0 suddenly, but correct EIP is placed on stack. I see some related changes in arch/x86_64/kernel/entry.S and will try to analyze it.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.