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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D60CDC433EF for ; Thu, 7 Apr 2022 20:35:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229803AbiDGUhH (ORCPT ); Thu, 7 Apr 2022 16:37:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37180 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230168AbiDGUg6 (ORCPT ); Thu, 7 Apr 2022 16:36:58 -0400 Received: from mail-pg1-f177.google.com (mail-pg1-f177.google.com [209.85.215.177]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 751BE35770C for ; Thu, 7 Apr 2022 13:23:05 -0700 (PDT) Received: by mail-pg1-f177.google.com with SMTP id k14so5976555pga.0 for ; Thu, 07 Apr 2022 13:23:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=cXJAXKnQvf0D6SNlG4wzqYhQvhJ7wKU7ytU/sf+RbQk=; b=gTWdAhfa51Uf6RqK2vZDLnAPE4FgtrP7oPYBax7uEJAIE5EfXGjamWJ+dr7cwmxqO5 qnLC5vBexFLSkOIYswqrBQJzoZy/ycMXaFxI+mF7MQ++8LQpYj59ppHnYBGN8TNZX6Lq 6yUILEDZRP+o5AWfmqmh6IRBkfIACaB2RLMowSce8yaw+fHG9+rilXwWOehy2zNuH1e0 I/LY2s6cAu7k/SXb5Y1AyM0N53qC77Wf98DdAQpMRNmJW3qMtVNCk/sGMjsLMcKTo/c7 3696VqCno3XEl1GQKuFWMj6nGLs1Opu4fPwWeNCeA+dcHIfwjwxgGX36CpJXYVhepYU3 NtGQ== X-Gm-Message-State: AOAM530aINe/J4hebzWcTtH7yzL1zOms83Zkbsy+4xkx5q9zOzQ7Hir2 sC9IbD3c28cdq7a5vnoIAwVSXji35PA= X-Google-Smtp-Source: ABdhPJy+zznpkBdf1Yvmcc+s2MIDd2eMI2jeV7kWUNBIaTRJtylmNiOUVpFQnNkM8AijV2k2kck1QA== X-Received: by 2002:a62:1d09:0:b0:4fd:8b00:d28 with SMTP id d9-20020a621d09000000b004fd8b000d28mr15929604pfd.81.1649360961135; Thu, 07 Apr 2022 12:49:21 -0700 (PDT) Received: from ?IPV6:2601:647:4000:d7:feaa:14ff:fe9d:6dbd? ([2601:647:4000:d7:feaa:14ff:fe9d:6dbd]) by smtp.gmail.com with ESMTPSA id me5-20020a17090b17c500b001c63699ff60sm10774116pjb.57.2022.04.07.12.49.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Apr 2022 12:49:20 -0700 (PDT) Message-ID: Date: Thu, 7 Apr 2022 12:49:18 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [bug report] rdma_rxe: WARNING: inconsistent lock state, inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage Content-Language: en-US To: Robert Pearson Cc: RDMA mailing list , Yi Zhang References: <1c16f053-0183-8343-9b36-62027c7260a8@acm.org> From: Bart Van Assche In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On 4/7/22 12:15, Robert Pearson wrote: > I would say it is very possible. There was a period when the pool > locks were switched to _bh spinlocks but that was later reversed back > to _irqsave locks which cleaned up some failures. > I don't know which version Yi Zhang was using. The root cause of this > bug was caused by > librdmacm making verbs API calls while holding _irqsave locks which I > didn't figure out until later. Hi Bob, I can reproduce the issue Yi reported with kernel v5.18-rc1. Please let me know if you need any additional information to reproduce this issue. Thanks, Bart.