BUG: corrupted list in rxrpc_put_call

8 views
Skip to first unread message

syzbot

unread,
Oct 3, 2020, 5:04:15 AM10/3/20
to da...@davemloft.net, dhow...@redhat.com, ku...@kernel.org, linu...@lists.infradead.org, linux-...@vger.kernel.org, net...@vger.kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: fcadab74 Merge tag 'drm-fixes-2020-10-01-1' of git://anong..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=143340a3900000
kernel config: https://syzkaller.appspot.com/x/.config?x=89ab6a0c48f30b49
dashboard link: https://syzkaller.appspot.com/bug?extid=e6326c848f3404ffb673
compiler: gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e6326c...@syzkaller.appspotmail.com

tipc: TX() has been purged, node left!
list_del corruption. next->prev should be ffff888000102c38, but was f000ff53f000e2c3
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:54!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 32547 Comm: kworker/u4:4 Not tainted 5.9.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: netns cleanup_net
RIP: 0010:__list_del_entry_valid.cold+0x48/0x55 lib/list_debug.c:54
Code: e8 51 9b 9b fd 0f 0b 4c 89 e2 48 89 ee 48 c7 c7 00 b4 d8 88 e8 3d 9b 9b fd 0f 0b 48 89 ee 48 c7 c7 c0 b4 d8 88 e8 2c 9b 9b fd <0f> 0b cc cc cc cc cc cc cc cc cc cc cc 41 57 41 56 41 55 41 54 55
RSP: 0018:ffffc900190ffa20 EFLAGS: 00010286
RAX: 0000000000000054 RBX: ffff888000102c38 RCX: 0000000000000000
RDX: ffff888097a50280 RSI: ffffffff815f59d5 RDI: fffff5200321ff36
RBP: ffff888000102c38 R08: 0000000000000054 R09: ffff8880ae4318e7
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88804e898010
R13: ffff888000000000 R14: ffff888000102c40 R15: 00000000000002b2
FS: 0000000000000000(0000) GS:ffff8880ae400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000334ea98 CR3: 000000009e10c000 CR4: 00000000001526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:132 [inline]
list_del_init include/linux/list.h:204 [inline]
rxrpc_put_call+0x17d/0x300 net/rxrpc/call_object.c:567
rxrpc_discard_prealloc+0x7e2/0xb30 net/rxrpc/call_accept.c:242
rxrpc_listen+0x11c/0x330 net/rxrpc/af_rxrpc.c:245
afs_close_socket+0x95/0x320 fs/afs/rxrpc.c:110
afs_net_exit+0x1c4/0x310 fs/afs/main.c:158
ops_exit_list+0xb0/0x160 net/core/net_namespace.c:186
cleanup_net+0x4ea/0xa00 net/core/net_namespace.c:603
process_one_work+0x94c/0x1670 kernel/workqueue.c:2269
worker_thread+0x64c/0x1120 kernel/workqueue.c:2415
kthread+0x3b5/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
Modules linked in:
---[ end trace e8b698dc6d68e2dc ]---
RIP: 0010:__list_del_entry_valid.cold+0x48/0x55 lib/list_debug.c:54
Code: e8 51 9b 9b fd 0f 0b 4c 89 e2 48 89 ee 48 c7 c7 00 b4 d8 88 e8 3d 9b 9b fd 0f 0b 48 89 ee 48 c7 c7 c0 b4 d8 88 e8 2c 9b 9b fd <0f> 0b cc cc cc cc cc cc cc cc cc cc cc 41 57 41 56 41 55 41 54 55
RSP: 0018:ffffc900190ffa20 EFLAGS: 00010286
RAX: 0000000000000054 RBX: ffff888000102c38 RCX: 0000000000000000
RDX: ffff888097a50280 RSI: ffffffff815f59d5 RDI: fffff5200321ff36
RBP: ffff888000102c38 R08: 0000000000000054 R09: ffff8880ae4318e7
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88804e898010
R13: ffff888000000000 R14: ffff888000102c40 R15: 00000000000002b2
FS: 0000000000000000(0000) GS:ffff8880ae400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000334ea98 CR3: 000000009e10c000 CR4: 00000000001526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Jan 29, 2021, 6:31:13 PM1/29/21
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages