From: syzbot <syzbot+ff11be94dfcd7a5af8da@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] [afs?] WARNING in rxrpc_send_data
Date: Thu, 12 Dec 2024 02:58:06 -0800 [thread overview]
Message-ID: <675ac1be.050a0220.20c8bc.0001.GAE@google.com> (raw)
In-Reply-To: <20241212033040.3361429-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in rxrpc_send_data
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6894 at net/rxrpc/sendmsg.c:296 rxrpc_alloc_txqueue net/rxrpc/sendmsg.c:296 [inline]
WARNING: CPU: 1 PID: 6894 at net/rxrpc/sendmsg.c:296 rxrpc_send_data+0x2969/0x2b30 net/rxrpc/sendmsg.c:390
Modules linked in:
CPU: 1 UID: 0 PID: 6894 Comm: syz.0.74 Not tainted 6.13.0-rc1-syzkaller-00407-g96b6fcc0ee41-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
RIP: 0010:rxrpc_alloc_txqueue net/rxrpc/sendmsg.c:296 [inline]
RIP: 0010:rxrpc_send_data+0x2969/0x2b30 net/rxrpc/sendmsg.c:390
Code: 24 48 48 89 de e8 37 35 ab f6 4c 39 f3 b8 00 fe ff ff 41 bf fc ff ff ff 44 0f 44 f8 45 31 f6 e9 71 fd ff ff e8 38 30 ab f6 90 <0f> 0b 90 48 8b 7c 24 28 e8 4a d0 09 f7 e9 46 fd ff ff 89 d9 80 e1
RSP: 0018:ffffc9000217f3a0 EFLAGS: 00010293
RAX: ffffffff8af441e8 RBX: ffff888064916500 RCX: ffff888030ef5a00
RDX: 0000000000000000 RSI: 00000000000000ff RDI: ffff8880792ee440
RBP: ffffc9000217f650 R08: ffff8880792ee43f R09: 0000000000000000
R10: ffff8880792ee340 R11: ffffed100f25dc88 R12: ffff8880649164c8
R13: 1ffff1100c922c9f R14: ffff8880792ee000 R15: 0000000000000000
FS: 00007fc5a3d7d6c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020005c00 CR3: 000000003143c000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
rxrpc_do_sendmsg+0x1569/0x1910 net/rxrpc/sendmsg.c:763
sock_sendmsg_nosec net/socket.c:711 [inline]
__sock_sendmsg+0x221/0x270 net/socket.c:726
____sys_sendmsg+0x52a/0x7e0 net/socket.c:2583
___sys_sendmsg net/socket.c:2637 [inline]
__sys_sendmmsg+0x36a/0x720 net/socket.c:2726
__do_sys_sendmmsg net/socket.c:2753 [inline]
__se_sys_sendmmsg net/socket.c:2750 [inline]
__x64_sys_sendmmsg+0xa0/0xb0 net/socket.c:2750
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc5a2f7ff19
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc5a3d7d058 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00007fc5a3145fa0 RCX: 00007fc5a2f7ff19
RDX: 0000000000000001 RSI: 0000000020005c00 RDI: 0000000000000003
RBP: 00007fc5a2ff3cc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fc5a3145fa0 R15: 00007ffd4836f878
</TASK>
Tested on:
commit: 96b6fcc0 Merge branch 'net-dsa-cleanup-eee-part-1'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12b084f8580000
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=11c2acdf980000
next parent reply other threads:[~2024-12-12 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241212033040.3361429-1-lizhi.xu@windriver.com>
2024-12-12 10:58 ` syzbot [this message]
[not found] <20241212142157.3707515-1-lizhi.xu@windriver.com>
2024-12-12 14:38 ` [syzbot] [net?] [afs?] WARNING in rxrpc_send_data syzbot
2024-12-10 8:27 syzbot
2024-12-10 14:44 ` syzbot
2024-12-12 17:57 ` David Howells
2024-12-12 18:26 ` 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=675ac1be.050a0220.20c8bc.0001.GAE@google.com \
--to=syzbot+ff11be94dfcd7a5af8da@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.