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 CD0F2E7E644 for ; Tue, 26 Sep 2023 15:37:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235137AbjIZPh6 (ORCPT ); Tue, 26 Sep 2023 11:37:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34428 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234874AbjIZPh5 (ORCPT ); Tue, 26 Sep 2023 11:37:57 -0400 Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 004A5120; Tue, 26 Sep 2023 08:37:49 -0700 (PDT) Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-40566f89f6eso61333935e9.3; Tue, 26 Sep 2023 08:37:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695742668; x=1696347468; darn=vger.kernel.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=mTYvK9pH/EJXRHP3ak9Ne9342oDswZw6qnzE3IYoQUw=; b=T+ZCMMeG5dwEoCr0UfBL43NshlTQN7hXNrykwx+eZS89urOTwA5qgRu2ZBCdAERfJt T6VRQ7KFFBBXYVBLwO3OpDU7dCAdXxH2pUcZcApfOGlZaCjfSVjgafmDIDIL0xoUh1V6 cIogswGhWBAV03+RFCFnndyuBZmXPV5wRgvRRsTgfOfmU30HJ9oyfezmiY0bGC5lCrzy rlde2hGJ8k8BQp5lB2eK+qDdEoe9/IBrsjhcalbhus7qJb1k8vMkfXHM1duAfRhqjp32 B76WAWwAyd6P9YgSY1yjPFOik98dVrh9na04KCTG+HGxNcrp26lpXLer+FikQrfTLlDQ Ut0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695742668; x=1696347468; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=mTYvK9pH/EJXRHP3ak9Ne9342oDswZw6qnzE3IYoQUw=; b=v1wNVPqE/anuWDXeMl1w454YfERh3gQpec89cHOlPYAyTOeLuz0Q+ctu6jOd/NI9gl 1o9dncYPQzQ8fOXaJGY7Godx3KL4rUCOHvgpUGCFgN0B3oJGFOfuA1h+4YbIzVk/+gkw jDfWhHkJqDwDNwOwvwoYA98Dprzq+JgAhmODahjyXyBxB/O0TXom8BxaGrEPNPsVdPeG r+aMgeUzMCPyTrCfuWjNcFMgpc/kTxXxHqbF7rQRgK7MNJhbcpPL3JCAOFv/vpA9Z3ee AXMevE2Vwka/PwenK3U1s791vVAfVmAxVVUlOYl2BokO0duLsbcwuAJV8CpNTLqSSmAs HmEg== X-Gm-Message-State: AOJu0YxL2bPDKowVhv4PIolu6vgpJ6Jj3Yo5e9wdMjSAe8DtWt4wThBP ub+jPe2rUo1PXz+aXM/c/vIEAaD7rg+sdWmqoqE= X-Google-Smtp-Source: AGHT+IGIvAA9vf46tqgTuoSwI1yLVXfkOJL2ScPNS/SeN+QUpnNWwvD2vjAwoCJfV3eo1gCrvU4e1nJi6newv0RbXNg= X-Received: by 2002:a05:600c:895:b0:405:95ae:4aa7 with SMTP id l21-20020a05600c089500b0040595ae4aa7mr4333702wmp.10.1695742668157; Tue, 26 Sep 2023 08:37:48 -0700 (PDT) MIME-Version: 1.0 References: <5a4efe6f-d8c6-84ce-377e-eb64bcad706c@linux.dev> <6fc3b524-af7d-43ce-aa05-5c44ec850b9b@acm.org> <02d7cbf2-b17b-488a-b6e9-ebb728b51c94@acm.org> <8aff9124-85c0-8e3b-dc35-1017b1540037@gmail.com> <3c84da83-cdbb-3326-b3f0-b2dee5f014e0@linux.dev> <4e7aac82-f006-aaa7-6769-d1c9691a0cec@gmail.com> <29c5de53-cc61-4efc-8e8d-690e27756a16@acm.org> <114ecd0b-42b0-4c1d-8b58-280e670550be@gmail.com> In-Reply-To: <114ecd0b-42b0-4c1d-8b58-280e670550be@gmail.com> From: Rain River Date: Tue, 26 Sep 2023 23:36:57 +0800 Message-ID: Subject: Re: [bug report] blktests srp/002 hang To: Bob Pearson Cc: Bart Van Assche , "Daisuke Matsuda (Fujitsu)" , Zhu Yanjun , Jason Gunthorpe , "leon@kernel.org" , Shinichiro Kawasaki , RDMA mailing list , "linux-scsi@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-scsi@vger.kernel.org On Tue, Sep 26, 2023 at 3:57=E2=80=AFAM Bob Pearson = wrote: > > On 9/25/23 10:00, Bart Van Assche wrote: > > On 9/24/23 21:47, Daisuke Matsuda (Fujitsu) wrote: > >> As Bob wrote above, nobody has found any logical failure in rxe > >> driver. > > > > That's wrong. In case you would not yet have noticed my latest email in > > this thread, please take a look at > > https://lore.kernel.org/linux-rdma/e8b76fae-780a-470e-8ec4-c6b650793d10= @leemhuis.info/T/#m0fd8ea8a4cbc27b37b042ae4f8e9b024f1871a73. I think the re= port in that email is a 100% proof that there is a use-after-free issue in = the rdma_rxe driver. Use-after-free issues have security implications and a= lso can cause data corruption. I propose to revert the commit that introduc= ed the rdma_rxe use-after-rpearson:src$ git clone git://git.kernel.org/pub/= scm/linux/git/rafael/linux-pm > Cloning into 'linux-pm'... > fatal: remote error: access denied or repository not exported: /pub/scm/l= inux/git/rafael/linux-pm > free unless someone comes up with a fix for the rdma_rxe driver. > > > > Bart. > > Bart, > > Having trouble following your recipe. The git repo you mention does not s= eem to be available. E.g. > > rpearson:src$ git clone git://git.kernel.org/pub/scm/linux/git/rafael/lin= ux-pm > Cloning into 'linux-pm'... > fatal: remote error: access denied or repository not exported: /pub/scm/l= inux/git/rafael/linux-pm > > I am not sure how to obtain the tag if I cannot see the repo. > > If I just try to enable KASAN by setting CONFIG_KASAN=3Dy in .config for = the current linux-rdma repo > and compile the kernel the kernel won't boot and is caught in some kind o= f SRSO hell. If I checkout > Linus' v6.4 tag and add CONFIG_KASAN=3Dy to a fresh .config file the kern= el builds OK but when I > try to boot it, it is unable to chroot to the root file system in boot. Bob, Suggested by a friend who is an expert in process schedule and workqueue, I made a test as below. On each CPU, a cpu-intensive process runs with high priority. Then run rxe with the commit, the rping almost can not work well. Without this commit, rping can work with rxe in the same scenario. When you fix this problem, consider the above. > > Any hints would be appreciated. > > Bob >