Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936896AbdCYBAa (ORCPT ); Fri, 24 Mar 2017 21:00:30 -0400 Received: from mail.kernel.org ([198.145.29.136]:39098 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935250AbdCYBAY (ORCPT ); Fri, 24 Mar 2017 21:00:24 -0400 Date: Fri, 24 Mar 2017 21:00:19 -0400 From: Steven Rostedt To: Sergey Senozhatsky Cc: Sebastian Ott , Petr Mladek , Heiko Carstens , linux-kernel@vger.kernel.org Subject: Re: lockdep warning: console vs. mem hotplug Message-ID: <20170324210019.23f4188f@gandalf.local.home> In-Reply-To: <20170325000005.GC6356@tigerII.localdomain> References: <20170324123933.78f9c125@gandalf.local.home> <20170325000005.GC6356@tigerII.localdomain> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 635 Lines: 21 On Sat, 25 Mar 2017 09:00:05 +0900 Sergey Senozhatsky wrote: > Hello, > > On (03/24/17 12:39), Steven Rostedt wrote: > [..] > > Is there a stack trace of where the lockdep dump happened? That is > > useful too. Otherwise we don't see where the inverse happened. > > Steven, isn't it the inversion I describe in [1] (after the first lockdep > warning)? > > [1] lkml.kernel.org/r/20170321044421.GB448@jagdpanzerIV.localdomain > Yeah, I believe you are right. I just wanted to make sure. It's the same backtrace as the "(&(&sclp_con_lock)->rlock){-.-...}:" dump, but I wanted to make sure. -- Steve