Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp3872168rwd; Mon, 22 May 2023 22:57:27 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ41ZH3PBRnk67JACORYmGH+mmsuWqBQhVEJRFQqANJzAWr8hGEW8c7ne1znWFA7pFB1lZz7 X-Received: by 2002:a05:6a20:6a1e:b0:103:b448:ddd8 with SMTP id p30-20020a056a206a1e00b00103b448ddd8mr15733688pzk.58.1684821446797; Mon, 22 May 2023 22:57:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684821446; cv=none; d=google.com; s=arc-20160816; b=VWTlSY2VEMbvssocvMozPNZJKAKERGbj0yNJGgodwQmpSZ03qWZ112Ku1KA+h2pP4+ vwXVwlPsofJYxFyJ3kaGykZ6rCx1P/bsuPrXMrx/8kea16WE+oQ+idmKZimwLdmP+n9J 1kKuqOnO/vcWsM9XN8h5bYM5+UMPS0B1x7QLpR7Z+UGANj9KBKA/Ahm2ApwNm5nTyh0o g72k0UhbruCgXDRqFrdzJ4586sbVi5wGLYan+CZiEU+ib9WbCXMgUOdV6XWYHY6DAD6t okD6Q1yI3AZ3gRZ4tMbQhSgf090q5ZPLUU0NHsbpn++X5A2NHy/46+IGJOG7KjWm/zVp nR/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:mime-version:date :dkim-signature:message-id; bh=IGxV7bRUi/GE13J/Uz6qtwRCl5Pm9NfAa4wWpSscMSs=; b=RAstKEHdHCcWB5kqQ+b4xOzdpaqju7Tpo6nuf56Ynkq6g8oW3808Krw7XcxUAGguZ6 pm/3cLbC1kRLPWCtH/TDAU+JD3h4iSJEY8rSqJVjVu02VUCrIN2ao4o2mf0KU2PN+DzH rulN0y6dZFsK/vmrG13E+W71ehRpSyAMx0HAcwiSIPQMryeomPHNyZ0oi3jTmVRWQ+FK 0eJ3vE6/krwa9Vz9575mtUxsOY3wS5MIy4Q7KPauBxjAUJfqwqso9gZnP6nSKdrOJ4FP pfbNBvcL+eC25ynkmsk7YdBkEJ8+GW4ouHI1yW5bdMSkkZi6FOfzp8bugwm1see8+UrK DawA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b=Nqx7uUOy; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id o15-20020a63920f000000b0053416d0b548si2054960pgd.543.2023.05.22.22.57.14; Mon, 22 May 2023 22:57:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b=Nqx7uUOy; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230153AbjEWFoS (ORCPT + 99 others); Tue, 23 May 2023 01:44:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44138 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231213AbjEWFoP (ORCPT ); Tue, 23 May 2023 01:44:15 -0400 Received: from out-61.mta0.migadu.com (out-61.mta0.migadu.com [IPv6:2001:41d0:1004:224b::3d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 19D25118 for ; Mon, 22 May 2023 22:44:14 -0700 (PDT) Message-ID: <5b6b8431-92c7-62df-299b-28f3a5f61d5f@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1684820650; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=IGxV7bRUi/GE13J/Uz6qtwRCl5Pm9NfAa4wWpSscMSs=; b=Nqx7uUOyUbn/ufMtUEQdd97JrXB+qKHU5OFZtzCCUCCn6fguKzx2BtSlvQ+p/gMRn4ODyg cMJq7Qv/wdkE4lDTXamqyuhMDatIAwhOT4BbKZl0I4EgCXPCpjsXWfwRfRB2G90+xlft6g GORT1nL91ifw7T9oUb402mlPC9rSBCU= Date: Tue, 23 May 2023 13:44:06 +0800 MIME-Version: 1.0 Subject: Re: [syzbot] [rdma?] INFO: trying to register non-static key in skb_dequeue (2) Content-Language: en-US To: Zhu Yanjun Cc: syzbot , jgg@ziepe.ca, leon@kernel.org, linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com References: <000000000000a589d005fc52ee2d@google.com> <13528f21-0f36-4fa2-d34f-eecee6720bc1@linux.dev> <0d515e17-5386-61ba-8278-500620969497@linux.dev> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Guoqing Jiang In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/23/23 13:18, Zhu Yanjun wrote: > On Tue, May 23, 2023 at 1:08 PM Zhu Yanjun wrote: >> On Tue, May 23, 2023 at 12:29 PM Zhu Yanjun wrote: >>> On Tue, May 23, 2023 at 12:10 PM Guoqing Jiang wrote: >>>> >>>> >>>> On 5/23/23 12:02, Zhu Yanjun wrote: >>>>> On Tue, May 23, 2023 at 11:47 AM Zhu Yanjun wrote: >>>>>> On Tue, May 23, 2023 at 10:26 AM Guoqing Jiang wrote: >>>>>>> >>>>>>> On 5/23/23 10:13, syzbot wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> syzbot tried to test the proposed patch but the build/boot failed: >>>>>>>> >>>>>>>> failed to apply patch: >>>>>>>> checking file drivers/infiniband/sw/rxe/rxe_qp.c >>>>>>>> patch: **** unexpected end of file in patch >>>>>> This is not the root cause. The fix is not good. >>>>> This problem is about "INFO: trying to register non-static key. The >>>>> code is fine but needs lockdep annotation, or maybe" >>> This warning is from "lock is not initialized". This is a >>> use-before-initialized problem. >>> The correct fix is to initialize the lock that is complained before it is used. >>> >>> Zhu Yanjun >> Based on the call trace, the followings are the order of this call trace. >> >> 291 /* called by the create qp verb */ >> 292 int rxe_qp_from_init(struct rxe_dev *rxe, struct rxe_qp *qp, >> struct rxe_pd *pd, >> 297 { >> ... >> 317 rxe_qp_init_misc(rxe, qp, init); >> ... >> 322 >> 323 err = rxe_qp_init_resp(rxe, qp, init, udata, uresp); >> 324 if (err) >> 325 goto err2; <--- error >> >> ... >> >> 334 err2: >> 335 rxe_queue_cleanup(qp->sq.queue); <--- Goto here >> 336 qp->sq.queue = NULL; >> >> In rxe_qp_init_resp, the error occurs before skb_queue_head_init. >> So this call trace appeared. > 250 static int rxe_qp_init_resp(struct rxe_dev *rxe, struct rxe_qp *qp, > 254 { > ... > 264 > 265 type = QUEUE_TYPE_FROM_CLIENT; > 266 qp->rq.queue = rxe_queue_init(rxe, &qp->rq.max_wr, > 267 wqe_size, type); > 268 if (!qp->rq.queue) > 269 return -ENOMEM; <---Error here > 270 > > ... > > 282 skb_queue_head_init(&qp->resp_pkts); <-this is not called. > ... > This will make spin_lock of resp_pkts is used before initialized. IMHO, the above is same as > Which is caused by "skb_queue_head_init(&qp->resp_pkts)" is not called > given rxe_qp_init_resp returns error, but the cleanup still trigger the > chain. > > rxe_qp_do_cleanup -> rxe_completer -> drain_resp_pkts -> > skb_dequeue(&qp->resp_pkts) my previous analysis. If not, could you provide another better way to fix it? Guoqing