From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S968424AbdAERIX (ORCPT <rfc822;w@1wt.eu>);
        Thu, 5 Jan 2017 12:08:23 -0500
Received: from arcturus.aphlor.org ([188.246.204.175]:54140 "EHLO
        arcturus.aphlor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S965111AbdAERIP (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 5 Jan 2017 12:08:15 -0500
Date: Thu, 5 Jan 2017 12:08:07 -0500
From: Dave Jones <davej@codemonkey.org.uk>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: stack unwinder warning.
Message-ID: <20170105170807.6fgtly5g3d672yuh@codemonkey.org.uk>
Mail-Followup-To: Dave Jones <davej@codemonkey.org.uk>,
        Josh Poimboeuf <jpoimboe@redhat.com>,
        Linux Kernel <linux-kernel@vger.kernel.org>
References: <20161227190030.dlyn24um2mcpbuzu@codemonkey.org.uk>
 <20170105145249.v2q3r3i46vzkg4au@treble>
 <20170105170214.sqf6rjywjgtxpbr2@treble>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170105170214.sqf6rjywjgtxpbr2@treble>
User-Agent: NeoMutt/20161126 (1.7.1)
X-Spam-Flag: skipped (authorised relay user)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Jan 05, 2017 at 11:02:14AM -0600, Josh Poimboeuf wrote:
 > On Thu, Jan 05, 2017 at 08:52:49AM -0600, Josh Poimboeuf wrote:
 > > On Tue, Dec 27, 2016 at 02:00:30PM -0500, Dave Jones wrote:
 > > > I'm not sure what to make of this. Josh ?  (4.10-rc1)
 > > > 
 > > > WARNING: kernel stack frame pointer at ffffc900003e7858 in trinity-c6:29122 has bad value ffffffff82103a80
 > > > unwind stack type:0 next_sp:          (null) mask:2 graph_idx:0
 > > > ffffc900003e7808: ffffffff811a02e5 (ring_buffer_lock_reserve+0x1d5/0x580)
 > > > ffffc900003e7810: ffffffff8119adc3 (rb_commit+0x93/0x350)
 > > > ffffc900003e7818: ffffffff811b31d4 (function_trace_call+0x104/0x1f0)
 > > > ffffc900003e7820: ffff8804f10ec000 (0xffff8804f10ec000)
 > > > ffffc900003e7828: 0000000000000000 ...
 > > > ffffc900003e7830: ffffffff8119b3ae (ring_buffer_unlock_commit+0x8e/0x120)
 > > > ffffc900003e7838: 0000000000000001 (0x1)
 > > > ffffc900003e7840: ffffea0002854e00 (0xffffea0002854e00)
 > > > ffffc900003e7848: 000000000000000a (0xa)
 > > > ffffc900003e7850: ffffea0002854ec0 (0xffffea0002854ec0)
 > > > ffffc900003e7858: ffffea000287c480 (0xffffea000287c480)
 > > 
 > > The value reported by the warning contradicts the value reported by the
 > > dump.  So this seems to have been caused by dumping the stack of a task
 > > which is running on another CPU.  There are still some places in the
 > > code where that's possible.  So I'm going to need to remove these
 > > unwinder warnings for now.
 > 
 > I'll be submitting the following patch soon, which I think should
 > silence the warning.  If the warning is recreatable, would you mind
 > testing it?

Sure. It usually spits it out pretty quickly. I'll give it a run..

	Dave