From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-173.mta1.migadu.com (out-173.mta1.migadu.com [95.215.58.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BEC8D2ED14D for ; Fri, 20 Jun 2025 15:24:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.173 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750433049; cv=none; b=sEzbbXvzetBaSwQdszXTHdmCGX5OwOllkFVrKroUENmgiJW1sme2ecCaddizCMcIBG/GMnAhD1YETKm3blNWua7wRxS4+Zk662eWuD6jn1zacuw6chG8BC9w0Yiln7cKgTUy+z6a1yyIg2LOlHv/kAmF9ahnBZzNXf/xq+ukyu0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750433049; c=relaxed/simple; bh=Ya3VNWrROgaFZ5bH5z9BWL5PtUUf3ZVrEfyqFiIGvkY=; h=Message-ID:Date:MIME-Version:Subject:From:To:References: In-Reply-To:Content-Type; b=q63yx5ZtLeFNkRIx63F0DbWPTHupIXoXVcKy1tCJ9azrk81xiy2EtNKRTtQWctvZQH+SDyO15Chx2G9idKgCVbS2Vlmnh26n3s7DB+K0hiGjZg2KYeJw/XaBzepFxFCuL7V/MkfhepNFDihlW6Uza06Iz9ezZ5AMo6E9jE+s7LE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=gtpx77gL; arc=none smtp.client-ip=95.215.58.173 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="gtpx77gL" Message-ID: <8a3ec239-7504-4c1a-86e7-4911be42e0a0@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1750433042; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=t363sv/PFQaoNjy1pWbaKZu3kCtrGkr9AZQHOKk936A=; b=gtpx77gLDK9Fm38E3p6Pi+Wuj/afpDwEXtOVz+E+LgFm0HRy1OeW//Sk0k9zlhRZqKt1Wc 78c+YmWk74v0cZECq4uNiD4TEnPuOkNVbLxmVsFjhBrmfJlRLDYoV+LmjWTG8QJo9JXW+U YZAu0afA+toFD0nY/1JZFRddXFf4Zu8= Date: Fri, 20 Jun 2025 08:23:48 -0700 Precedence: bulk X-Mailing-List: linux-rdma@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [syzbot] Monthly rdma report (Jun 2025) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Zhu Yanjun To: syzbot , linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org, syzkaller-bugs@googlegroups.com References: <68552aae.a00a0220.137b3.003f.GAE@google.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT 在 2025/6/20 8:12, Zhu Yanjun 写道: > 在 2025/6/20 2:32, syzbot 写道: >> Hello rdma maintainers/developers, >> >> This is a 31-day syzbot report for the rdma subsystem. >> All related reports/information can be found at: >> https://syzkaller.appspot.com/upstream/s/rdma >> >> During the period, 0 new issues were detected and 0 were fixed. >> In total, 8 issues are still open and 65 have already been fixed. >> >> Some of the still happening issues: >> >> Ref Crashes Repro Title >> <1> 462     No    INFO: task hung in rdma_dev_change_netns >>                    https://syzkaller.appspot.com/bug? >> extid=73c5eab674c7e1e7012e >> <2> 338     Yes   WARNING in rxe_pool_cleanup >>                    https://syzkaller.appspot.com/bug? >> extid=221e213bf17f17e0d6cd >> <3> 72      No    INFO: task hung in add_one_compat_dev (3) >>                    https://syzkaller.appspot.com/bug? >> extid=6dee15fdb0606ef7b6ba >> <4> 50      No    INFO: task hung in rdma_dev_exit_net (6) >>                    https://syzkaller.appspot.com/bug? >> extid=3658758f38a2f0f062e7 >> <5> 28      Yes   WARNING in gid_table_release_one (3) >>                    https://syzkaller.appspot.com/bug? >> extid=b0da83a6c0e2e2bddbd4 >> <6> 5       No    WARNING in rxe_skb_tx_dtor >>                    https://syzkaller.appspot.com/bug? >> extid=8425ccfb599521edb153 > > To this rxe_skb_tx_dtor problem, I think I have posted a fix. Do you > make tests with it? Should I file an official commit to confirm if this problem is fixed or not? Yanjun.Zhu > > The link should be: https://lore.kernel.org/ > all/6813a531.050a0220.14dd7d.0018.GAE@google.com/T/ > > Best Regards, > Yanjun.Zhu > >> >> --- >> This report is generated by a bot. It may contain errors. >> See https://goo.gl/tpsmEJ for more information about syzbot. >> syzbot engineers can be reached at syzkaller@googlegroups.com. >> >> To disable reminders for individual bugs, reply with the following >> command: >> #syz set no-reminders >> >> To change bug's subsystems, reply with: >> #syz set subsystems: new-subsystem >> >> You may send multiple commands in a single email message. > -- Best Regards, Yanjun.Zhu