From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754988AbcBVM04 (ORCPT ); Mon, 22 Feb 2016 07:26:56 -0500 Received: from casper.infradead.org ([85.118.1.10]:47624 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754840AbcBVM0z (ORCPT ); Mon, 22 Feb 2016 07:26:55 -0500 Date: Mon, 22 Feb 2016 13:26:51 +0100 From: Peter Zijlstra To: Wang Yufen Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, guohanjun@huawei.com, dingtianhong@huawei.com, Ma Jun Subject: Re: [PATCH] trace/irq: fix WARNING in check_flags while CONFIG_TRACE_IRQFLAGS opened Message-ID: <20160222122651.GG6357@twins.programming.kicks-ass.net> References: <1456135605-8888-1-git-send-email-wangyufen@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1456135605-8888-1-git-send-email-wangyufen@huawei.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 22, 2016 at 06:06:45PM +0800, Wang Yufen wrote: > if CONFIG_TRACE_IRQFLAGS opened, we got that warning: > [ 214.078880] ------------[ cut here ]------------ > > [ 214.083521] WARNING: CPU: 4 PID: 1 at kernel/locking/lockdep.c:3557 > check_flags.part.40+0x1c0/0x1d0() I'm not entirely sure how to open a CONFIG_ symbol, but when I have it enabled, I do not get this warning. So your report is missing some critical information.