BUG: unable to handle kernel paging request in quarantine_remove_cache (2)

5 zobrazení
Přeskočit na první nepřečtenou zprávu

syzbot

nepřečteno,
25. 12. 2020 6:49:1625.12.20
komu: syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f2ecb86 Linux 4.14.212
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1335ec2b500000
kernel config: https://syzkaller.appspot.com/x/.config?x=80549830ca6ffbb2
dashboard link: https://syzkaller.appspot.com/bug?extid=0b9b28971b405827e600
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+0b9b28...@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at 0000070707000707
IP: qlist_move_cache+0x67/0xd0 mm/kasan/quarantine.c:275
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 138 Comm: kworker/u4:3 Not tainted 4.14.212-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: netns cleanup_net
task: ffff8880b5218000 task.stack: ffff8880b5220000
RIP: 0010:qlist_move_cache+0x67/0xd0 mm/kasan/quarantine.c:275
RSP: 0018:ffff8880b5227b38 EFLAGS: 00010002
RAX: ffff8880000623c0 RBX: ffff8880b5227b70 RCX: ffffea000000189f
RDX: 0000000000001100 RSI: ffff8880b5227b70 RDI: ffff888000124400
RBP: ffff888057a45800 R08: ffffffff8b9b1d60 R09: 00000000000c00ca
R10: ffff8880b5218978 R11: ffff8880b5218000 R12: ffffea0000000000
R13: 0000070707000707 R14: ffffffff8becba90 R15: 0000070707000707
FS: 0000000000000000(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000070707000707 CR3: 00000000a9bc3000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
quarantine_remove_cache+0x63/0xd0 mm/kasan/quarantine.c:317
shutdown_cache+0xe/0x1e0 mm/slab_common.c:540
kmem_cache_destroy+0x1d2/0x240 mm/slab_common.c:842
tipc_server_stop+0x13a/0x171 net/tipc/server.c:637
tipc_topsrv_stop net/tipc/subscr.c:390 [inline]
tipc_topsrv_exit_net+0x168/0x28a net/tipc/subscr.c:402
ops_exit_list+0xa5/0x150 net/core/net_namespace.c:142
cleanup_net+0x3b3/0x840 net/core/net_namespace.c:484
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 00 00 00 00 eb 22 49 83 3e 00 74 7d 49 8b 46 08 4c 89 28 4d 89 6e 08 49 c7 45 00 00 00 00 00 49 01 56 10 4d 85 ff 74 56 4d 89 fd <4d> 8b 3f 4c 89 ef e8 0e be a4 ff 48 c1 e8 0c 48 c1 e0 06 4c 01
RIP: qlist_move_cache+0x67/0xd0 mm/kasan/quarantine.c:275 RSP: ffff8880b5227b38
CR2: 0000070707000707
---[ end trace de0785436ec911b2 ]---


---
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

nepřečteno,
24. 4. 2021 7:49:1824.04.21
komu: syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Odpovědět všem
Odpověď autorovi
Přeposlat
0 nových zpráv