[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrX1a8Bg=4qgDTPry1GUaWqQHprt+5JbvJJR=2eEa=33MA@mail.gmail.com>
Date: Sun, 18 Oct 2015 09:12:53 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Stas Sergeev <stsp@...t.ru>
Cc: Denys Vlasenko <dvlasenk@...hat.com>,
Pavel Emelyanov <xemul@...allels.com>,
Borislav Petkov <bp@...en8.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Cyrill Gorcunov <gorcunov@...il.com>,
Brian Gerst <brgerst@...il.com>, X86 ML <x86@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [RFC 3/4] x86/signal/64: Re-add support for SS in the 64-bit
signal context
On Sun, Oct 18, 2015 at 6:36 AM, Stas Sergeev <stsp@...t.ru> wrote:
> 15.10.2015 00:41, Andy Lutomirski пишет:
>>>
>>> If this my
>>> understanding is correct and the flag is just an indication rather
>>> than a requested action, perhaps the name should be different,
>>> e.g. UC_SIG_FROM_32BIT or the like?
>>> Anyway, this is minor. :)
>>> I'll try to test the patch within a few days, thanks for you time!
>>
>> No problem. Thanks for being willing to test!
>
> Hello Andy, I am unlucky at testing this.
> dosemu doesn't even start for me on the git kernels.
> After a half day of debugging, it seems the kernel forgets
> to fill in the "err" field in the sigcontext struct when
> page fault occurs. That confuses the dosemu's instruction
> decoder.
> Does this ring any bells?
No, but I can reproduce it on some kernels. Let me see if I can fix it, too.
--Andy
--
Andy Lutomirski
AMA Capital Management, LLC
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists