Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753443AbbBYN4I (ORCPT ); Wed, 25 Feb 2015 08:56:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51361 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752503AbbBYN4E (ORCPT ); Wed, 25 Feb 2015 08:56:04 -0500 Message-ID: <54EDD456.5010606@redhat.com> Date: Wed, 25 Feb 2015 14:55:34 +0100 From: Denys Vlasenko User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Andrey Wagin CC: Andy Lutomirski , Linus Torvalds , Oleg Nesterov , Borislav Petkov , "H. Peter Anvin" , Frederic Weisbecker , X86 ML , Alexei Starovoitov , Will Drewry , Kees Cook , LKML Subject: Re: [PATCH 2/3 v3] x86: entry_64.S: always allocate complete "struct pt_regs" References: <1423778052-21038-1-git-send-email-dvlasenk@redhat.com> <1423778052-21038-2-git-send-email-dvlasenk@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1324 Lines: 42 On 02/25/2015 01:37 PM, Andrey Wagin wrote: > 2015-02-13 0:54 GMT+03:00 Denys Vlasenko : > My test vm doesn't boot with this patch. Could you help to investigate > this issue? Hi Andrey, thanks for testing! > I have attached a kernel config and console log. Looking at the logs, it seems that regular syscalls do work: systemd managed to function for some time, even spawned a few children. It might be that the bug is somewhere in signal delivery code. This would explain why oops got delayed. I am trying to reproduce it. My gcc seems to be a bit old - it can't digest CONFIG_CC_STACKPROTECTOR_STRONG=y in your .config. I switched to using "only" CONFIG_CC_STACKPROTECTOR_REGULAR=y: CONFIG_CC_STACKPROTECTOR=y # CONFIG_CC_STACKPROTECTOR_NONE is not set CONFIG_CC_STACKPROTECTOR_REGULAR=y # CONFIG_CC_STACKPROTECTOR_STRONG is not set and resulting kernel works for me. Can you send me your bzImage (off-list, of course)? I'll send you my qemu test setup, can you check whether crash is happening for you when you run your kernel in it? -- vda -- 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/