From: syzbot <syzbot+ff11be94dfcd7a5af8da@syzkaller.appspotmail.com>
To: davem@davemloft.net, dhowells@redhat.com, edumazet@google.com,
horms@kernel.org, kuba@kernel.org,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
marc.dionne@auristor.com, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] [afs?] WARNING in rxrpc_send_data
Date: Thu, 12 Dec 2024 10:26:02 -0800 [thread overview]
Message-ID: <675b2aba.050a0220.599f4.00b8.GAE@google.com> (raw)
In-Reply-To: <2863838.1734026244@warthog.procyon.org.uk>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+ff11be94dfcd7a5af8da@syzkaller.appspotmail.com
Tested-by: syzbot+ff11be94dfcd7a5af8da@syzkaller.appspotmail.com
Tested on:
commit: f3674384 Merge branch 'net-smc-two-features-for-smc-r'
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=13a34d44580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1362a5aee630ff34
dashboard link: https://syzkaller.appspot.com/bug?extid=ff11be94dfcd7a5af8da
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=169d4d44580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-12-12 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 8:27 [syzbot] [net?] [afs?] WARNING in rxrpc_send_data syzbot
2024-12-10 14:44 ` syzbot
2024-12-12 3:30 ` [syzbot] " syzbot
2024-12-12 14:22 ` syzbot
2024-12-12 17:57 ` David Howells
2024-12-12 18:26 ` syzbot [this message]
[not found] <20241212033040.3361429-1-lizhi.xu@windriver.com>
2024-12-12 10:58 ` syzbot
[not found] <20241212142157.3707515-1-lizhi.xu@windriver.com>
2024-12-12 14:38 ` 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=675b2aba.050a0220.599f4.00b8.GAE@google.com \
--to=syzbot+ff11be94dfcd7a5af8da@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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