From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932421AbdCGCFO (ORCPT ); Mon, 6 Mar 2017 21:05:14 -0500 Received: from mail-ua0-f178.google.com ([209.85.217.178]:35496 "EHLO mail-ua0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752742AbdCGCFF (ORCPT ); Mon, 6 Mar 2017 21:05:05 -0500 MIME-Version: 1.0 X-Originating-IP: [118.200.139.147] In-Reply-To: <20170306164008.dgg3xthl2ihsdfnu@treble> References: <20170227154727.lbfvtizqzzybekjz@treble> <20170306164008.dgg3xthl2ihsdfnu@treble> From: Daniel J Blueman Date: Tue, 7 Mar 2017 10:04:11 +0800 Message-ID: Subject: Re: stack frame unwindind KASAN errors To: Josh Poimboeuf Cc: Linux Kernel , Ingo Molnar Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7 March 2017 at 00:40, Josh Poimboeuf wrote: > On Mon, Mar 06, 2017 at 02:52:01PM +0800, Daniel J Blueman wrote: >> Thanks Josh! >> >> With this patch, the KASAN warning still occurs, but at >> unwind_get_return_address+0x1d3/0x130 instead; the rest of the trace >> is identical. >> >> (gdb) list *(unwind_get_return_address+0x1d3) >> 0xffffffff8112bca3 is in unwind_get_return_address >> (./include/linux/compiler.h:243). >> 238 }) >> 239 >> 240 static __always_inline >> 241 void __read_once_size(const volatile void *p, void *res, int size) >> 242 { >> 243 __READ_ONCE_SIZE; > > Looking deeper, I have an idea about what's going on: > > https://quora.org/dmesg.txt > > Each of the warnings seems to show an interrupt happening during an EFI > call. I'm guessing EFI modified the frame pointer, at least > temporarily, which confused the unwinder :-( > > Would it be possible for you to test again with 4.10? It has some > additional unwinder output which should hopefully confirm my suspicions. Very good; I don't see the KASAN warnings with 4.10 in the same environment. Thanks, Daniel -- Daniel J Blueman