public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: syzbot <syzbot+8425ccfb599521edb153@syzkaller.appspotmail.com>,
	jgg@ziepe.ca, leon@kernel.org, linux-kernel@vger.kernel.org,
	linux-rdma@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [rdma?] WARNING in rxe_skb_tx_dtor
Date: Sun, 6 Jul 2025 14:04:55 -0700	[thread overview]
Message-ID: <f870e739-bbe7-4260-a847-1035f1c5b801@linux.dev> (raw)
In-Reply-To: <6865d59b.a70a0220.5d25f.0781.GAE@google.com>

在 2025/7/2 17:58, syzbot 写道:
> Hello,
> 
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Today I made tests with rdma-core after this patch is applied on the 
linux upstream. All the test cases in rdma-core can pass successfully.

I will send this commit out based on the rdma next repository.

Zhu Yanjun

> 
> Reported-by: syzbot+8425ccfb599521edb153@syzkaller.appspotmail.com
> Tested-by: syzbot+8425ccfb599521edb153@syzkaller.appspotmail.com
> 
> Tested on:
> 
> commit:         6f8d023e RDMA/rxe: Fix rxe_skb_tx_dtor problem
> git tree:       https://github.com/zhuyj/linux.git v6.16_fix_rxe_skb_tx_dtor
> console output: https://syzkaller.appspot.com/x/log.txt?x=13973770580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=36b0e72cad5298f8
> dashboard link: https://syzkaller.appspot.com/bug?extid=8425ccfb599521edb153
> compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
> 
> Note: no patches were applied.
> Note: testing is done by a robot and is best-effort only.


  reply	other threads:[~2025-07-06 21:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <685f29f2.a00a0220.274b5f.0003.GAE@google.com>
2025-06-27 23:42 ` [syzbot] [rdma?] WARNING in rxe_skb_tx_dtor Yanjun.Zhu
2025-07-03  0:36   ` Yanjun.Zhu
2025-07-03  0:58     ` syzbot
2025-07-06 21:04       ` Zhu Yanjun [this message]
2025-05-01 16:45 syzbot
2025-05-02  9:54 ` Zhu Yanjun
2025-05-13 14:57   ` Zhu Yanjun
2025-06-26 20:55 ` syzbot
2025-06-26 22:22   ` Yanjun.Zhu
2025-06-26 22:25     ` syzbot
2025-06-26 22:38       ` Yanjun.Zhu
2025-06-26 22:54         ` syzbot
2025-06-27  2:49         ` Zhu Yanjun
2025-06-27  3:11           ` syzbot
2025-06-27  3:41             ` Zhu Yanjun
2025-06-27  3:57               ` syzbot
2025-06-27  4:53                 ` Zhu Yanjun
2025-06-27  5:09                   ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f870e739-bbe7-4260-a847-1035f1c5b801@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=syzbot+8425ccfb599521edb153@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox