From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1CE84C433F5 for ; Thu, 2 Sep 2021 19:06:31 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id AF0BE6054E for ; Thu, 2 Sep 2021 19:06:30 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org AF0BE6054E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 56AAA6B0071; Thu, 2 Sep 2021 15:06:30 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 51A0A900003; Thu, 2 Sep 2021 15:06:30 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4098C900002; Thu, 2 Sep 2021 15:06:30 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0034.hostedemail.com [216.40.44.34]) by kanga.kvack.org (Postfix) with ESMTP id 32EE26B0071 for ; Thu, 2 Sep 2021 15:06:30 -0400 (EDT) Received: from smtpin02.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id DAB70182890F0 for ; Thu, 2 Sep 2021 19:06:29 +0000 (UTC) X-FDA: 78543564498.02.ADE94DF Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf14.hostedemail.com (Postfix) with ESMTP id 9DA2A600198D for ; Thu, 2 Sep 2021 19:06:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=0yRZmL5nhWDE48aMzkFfEXo04VyWR0hoUp+NXB3KQqU=; b=ivip0gQES2s93NQsau0LACmosP 3+/LznRjJzoEg/EoI4FQMR3kFYFIowMcDeSvoOAq3SB1cmH1VIw+C11/mrxiIPyX+x1jfX0jLRuA5 /mZS8r6dZtIyqPJahh4HTFzl7jAUp58uYsQ80WNzl1YqMR/geDrqosW3kE8K8pDS8O50KE0ZdHvms nEGU8+LPWWqkX8Uh/V++DlqwalwuwOnmVS+7zCpmgFOfJZKQ5Qss23gCMf6XJ01br/pubQvT2H1Bo Yxu9uol//N1sZPZdASAWs+mdLKa8iovK2Gu+4PZK2BuYW7F846cN4oPlq/VXqWYg1SJOvzWjbpwg0 qt0AtZpw==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1mLrz6-003kqT-GC; Thu, 02 Sep 2021 19:03:11 +0000 Date: Thu, 2 Sep 2021 20:02:48 +0100 From: Matthew Wilcox To: Jens Axboe Cc: LKML , Thomas Gleixner , Christoph Lameter , Linux Memory Management List Subject: Re: slub: BUG: Invalid wait context Message-ID: References: <3b7661a1-dbde-ea54-f880-99777c95ae22@kernel.dk> <91af18d0-64cb-71ac-e9f4-4135fe02cb33@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <91af18d0-64cb-71ac-e9f4-4135fe02cb33@kernel.dk> Authentication-Results: imf14.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=ivip0gQE; dmarc=none; spf=none (imf14.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: 9DA2A600198D X-Stat-Signature: gjj6w9id87196wb7tri97w5cbh9juqms X-HE-Tag: 1630609589-353788 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Sep 02, 2021 at 12:59:33PM -0600, Jens Axboe wrote: > On 9/2/21 12:56 PM, Matthew Wilcox wrote: > > On Thu, Sep 02, 2021 at 10:22:23AM -0600, Jens Axboe wrote: > >> Hi, > >> > >> Booting current -git yields the below splat. I'm assuming this is > >> related to the new RT stuff, where spin_lock() can sleep. This obviously > >> won't fly off IPI. > > > > You want to turn off PROVE_RAW_LOCK_NESTING for the moment. > > Because? help Enable the raw_spinlock vs. spinlock nesting checks which ensure that the lock nesting rules for PREEMPT_RT enabled kernels are not violated. NOTE: There are known nesting problems. So if you enable this option expect lockdep splats until these problems have been fully addressed which is work in progress. This config switch allows to identify and analyze these problems. It will be removed and the check permanently enabled once the main issues have been fixed. If unsure, select N.