From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751174AbeAVRkg (ORCPT ); Mon, 22 Jan 2018 12:40:36 -0500 Received: from bombadil.infradead.org ([65.50.211.133]:55671 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751028AbeAVRkf (ORCPT ); Mon, 22 Jan 2018 12:40:35 -0500 Date: Mon, 22 Jan 2018 18:40:31 +0100 From: Peter Zijlstra To: Tejun Heo Cc: Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: Spurious lockdep splat in v4.15-rc9 Message-ID: <20180122174031.GG2228@hirez.programming.kicks-ass.net> References: <20180122171018.GF1096857@devbig577.frc2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180122171018.GF1096857@devbig577.frc2.facebook.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 22, 2018 at 09:10:18AM -0800, Tejun Heo wrote: > Hello, Peter, Ingo. > > I get the below lockdep warning if I try to write a config into cgroup > cpu.max file. It's warning about A-A deadlock, but it's obviously > spurious - the system doesn't lock up and the warning is about two > get_online_cpus() calls nesting. Looks real, just not instantly fatal. It would generate an actual deadlock the moment there is a contending hotplug operation around though. I'll have a wee look.