From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 0E52FC77B75
	for <linux-kernel@archiver.kernel.org>; Tue, 18 Apr 2023 22:08:33 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S233130AbjDRWIc (ORCPT <rfc822;linux-kernel@archiver.kernel.org>);
        Tue, 18 Apr 2023 18:08:32 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46982 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S231522AbjDRWI3 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 18 Apr 2023 18:08:29 -0400
Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 73A1F269F
        for <linux-kernel@vger.kernel.org>; Tue, 18 Apr 2023 15:08:28 -0700 (PDT)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by dfw.source.kernel.org (Postfix) with ESMTPS id 0FA1A615CD
        for <linux-kernel@vger.kernel.org>; Tue, 18 Apr 2023 22:08:28 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1ED60C433D2;
        Tue, 18 Apr 2023 22:08:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org;
        s=korg; t=1681855707;
        bh=A8qCPR0691ECOrXmuz6X4xvdj4xXQbRWYqn0vXEFJrI=;
        h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
        b=L9qKdnuaAkHDdGDGC7hXjBWiX9KmdmBTUh1GRDLQHPGN553w+QtJFPUC5VbEX5Zmc
         81wR2O0zW6CUSFEnMdGnQ4RGveVxBJvFoOHv0SXFwkaOv/ULg+gtc4bxjFtu4vdSVj
         rmqV+cndvX5R43kZJQyqA005bl/FJtu/0m6zpoRI=
Date:   Tue, 18 Apr 2023 15:08:26 -0700
From:   Andrew Morton <akpm@linux-foundation.org>
To:     Zqiang <qiang1.zhang@intel.com>
Cc:     elver@google.com, ryabinin.a.a@gmail.com, glider@google.com,
        andreyknvl@gmail.com, dvyukov@google.com,
        kasan-dev@googlegroups.com, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kasan: Fix lockdep report invalid wait context
Message-Id: <20230418150826.ae36090243b21f21f3265792@linux-foundation.org>
In-Reply-To: <20230327120019.1027640-1-qiang1.zhang@intel.com>
References: <20230327120019.1027640-1-qiang1.zhang@intel.com>
X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 27 Mar 2023 20:00:19 +0800 Zqiang <qiang1.zhang@intel.com> wrote:

> For kernels built with the following options and booting
> 
> CONFIG_SLUB=y
> CONFIG_DEBUG_LOCKDEP=y
> CONFIG_PROVE_LOCKING=y
> CONFIG_PROVE_RAW_LOCK_NESTING=y
> 
> [    0.523115] [ BUG: Invalid wait context ]

Could we please get some reviewer input on this change?

Thanks.