Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp3354922pxu; Mon, 30 Nov 2020 00:45:03 -0800 (PST) X-Google-Smtp-Source: ABdhPJwDriqRrlxAj3OFLlV33gsfT+1Paz06lMB10pOClldiWnXsbKdR0M/MDVvuswWm3Al60C8f X-Received: by 2002:a17:906:c24b:: with SMTP id bl11mr19664923ejb.3.1606725903659; Mon, 30 Nov 2020 00:45:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606725903; cv=none; d=google.com; s=arc-20160816; b=QKWBP5t6aRBnc9wTFD8vLSK50WkXQ4lVbBBeAhqug3HAchIQ503NQUgK5ta6/THEwT Rpv5s94FwCtAeoRCIILjlWsoDx3kgp8JKOEvGdn3nL/oC3c1mEGakwdTrRpmF86bXfai t9p2osTCzEVGy5iJS0LmlciKNuluhHxwapKUyTBi8S8vxhUoE9qPDkO6L3FKa+TCzYjB vnlhJijx0fHgWTAZlHiDUF0vB1zhzgh9Z/8NdqI9ZQu9mI8MSLXcS3M9YBuNTpF9pgRx HwKxcKLJR7lbYXX+8ciepBFkoHMHOSnKMwvsr+dUGehJQ/Qgfbhufrrk41B5v6hfdP52 VaLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:from:subject:message-id:date:mime-version; bh=Sc8rQuAJBKv+/HrAfD4yy+MSmV2CTQJerzZ7v9NKufU=; b=wogyrnZb9vHWn4GHdpGAU23nLcnuslkssjM3YEnM8oIKe8pvNdY2oQya2phfWpBsO2 2r+xGfzMd1aoQ6qPshVK6Bz1ogTmK8Yn/02U/dkt9IcBZAPn0m13BOreFy0mgwWZ8xsX Vt8Carjxz1zU/eAd5/VWhRpM0ttRBkQqYhQ+lmj3sJslnGWAsuATpw+q4ywYcg2aXf4v pUNE/N7D6r0kBRB7M7tBhpxGuoiPJKtQUtfYrGB36zW4Fh16MavX0SNvVtoWUoNH8oD+ 4VSl0BGllguRlooZjboxjae0F899ttHEwtPCAGc+62FQTQfiJH8oGazH+wC+0v35EIFD YbJg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ce21si8142634edb.306.2020.11.30.00.44.39; Mon, 30 Nov 2020 00:45:03 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726623AbgK3Ik7 (ORCPT + 99 others); Mon, 30 Nov 2020 03:40:59 -0500 Received: from mail-il1-f198.google.com ([209.85.166.198]:36423 "EHLO mail-il1-f198.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725902AbgK3Ik6 (ORCPT ); Mon, 30 Nov 2020 03:40:58 -0500 Received: by mail-il1-f198.google.com with SMTP id r3so9525663ila.3 for ; Mon, 30 Nov 2020 00:40:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=Sc8rQuAJBKv+/HrAfD4yy+MSmV2CTQJerzZ7v9NKufU=; b=hOYkNccVwFxowCjON6pRoFpYp1nJ9M8BbHv92diSjAwMD2ZrQVqmFP0zfoVirQAOHJ trhqplijX2FbWJ14pZj1tPDKaaYEEBNlxRxVuSc/pSseVSgKCsuCkou6trIMCuoYccs1 KcCTgyJerjuMN4Sm/qDNqLodV1htdinfZz7PEFPYhIEI4uYwY9ONL7+4oHx/NvpTj+w4 7934TLwCAojolJ26zUzU2mNkV45VpPGsLWip8jDgye0rrQSJmaYhR+uOBfyeUhgo0AEj lJQyoEpeFUcmGJAhnrRsQnsvkbsBvJIc44onKpXpnkkQcGCu8WAh1pbVzYspIyDnP6ZA brWg== X-Gm-Message-State: AOAM5334B5mrKNuHDpFZ7oKtvD57Xgru/2VRnmZ0wCBSZUjXBpmby2p7 42dPgUyKFi0pdBHL4SzfmZ2h48zBOWOKymf/zW6HbVXgH3oH MIME-Version: 1.0 X-Received: by 2002:a92:aa53:: with SMTP id j80mr17846552ili.88.1606725617876; Mon, 30 Nov 2020 00:40:17 -0800 (PST) Date: Mon, 30 Nov 2020 00:40:17 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000b4862805b54ef573@google.com> Subject: WARNING in sk_stream_kill_queues (5) From: syzbot To: akpm@linux-foundation.org, davem@davemloft.net, dvyukov@google.com, elver@google.com, glider@google.com, jannh@google.com, kuba@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 6147c83f Add linux-next specific files for 20201126 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=117c9679500000 kernel config: https://syzkaller.appspot.com/x/.config?x=9b91566da897c24f dashboard link: https://syzkaller.appspot.com/bug?extid=7b99aafdcc2eedea6178 compiler: gcc (GCC) 10.1.0-syz 20200507 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103bf743500000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167c60c9500000 The issue was bisected to: commit 145cd60fb481328faafba76842aa0fd242e2b163 Author: Alexander Potapenko Date: Tue Nov 24 05:38:44 2020 +0000 mm, kfence: insert KFENCE hooks for SLUB bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13abe5b3500000 final oops: https://syzkaller.appspot.com/x/report.txt?x=106be5b3500000 console output: https://syzkaller.appspot.com/x/log.txt?x=17abe5b3500000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+7b99aafdcc2eedea6178@syzkaller.appspotmail.com Fixes: 145cd60fb481 ("mm, kfence: insert KFENCE hooks for SLUB") ------------[ cut here ]------------ WARNING: CPU: 0 PID: 11307 at net/core/stream.c:207 sk_stream_kill_queues+0x3c3/0x530 net/core/stream.c:207 Modules linked in: CPU: 0 PID: 11307 Comm: syz-executor673 Not tainted 5.10.0-rc5-next-20201126-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:sk_stream_kill_queues+0x3c3/0x530 net/core/stream.c:207 Code: 00 00 00 fc ff df 48 c1 ea 03 0f b6 04 02 84 c0 74 08 3c 03 0f 8e 63 01 00 00 8b ab 20 02 00 00 e9 60 ff ff ff e8 ad 24 7b fa <0f> 0b eb 97 e8 a4 24 7b fa 0f 0b eb a0 e8 9b 24 7b fa 0f 0b e9 a5 RSP: 0018:ffffc9000979f978 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 00000000fffffe80 RCX: ffffffff86f5877a RDX: ffff88801ebb5040 RSI: ffffffff86f587e3 RDI: 0000000000000005 RBP: 0000000000000180 R08: 0000000000000001 R09: ffffffff8ebd9817 R10: 0000000000000000 R11: 0000000000000001 R12: ffff8880182f3ce0 R13: ffffffff8fb178c0 R14: ffff8880182f3ae8 R15: ffff8880182f3c70 FS: 0000000000000000(0000) GS:ffff8880b9e00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000004c7cd8 CR3: 000000000b08e000 CR4: 00000000001506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: inet_csk_destroy_sock+0x1a5/0x490 net/ipv4/inet_connection_sock.c:885 __tcp_close+0xd3e/0x1170 net/ipv4/tcp.c:2585 tcp_close+0x29/0xc0 net/ipv4/tcp.c:2597 inet_release+0x12e/0x280 net/ipv4/af_inet.c:431 __sock_release+0xcd/0x280 net/socket.c:596 sock_close+0x18/0x20 net/socket.c:1255 __fput+0x283/0x920 fs/file_table.c:280 task_work_run+0xdd/0x190 kernel/task_work.c:140 exit_task_work include/linux/task_work.h:30 [inline] do_exit+0xb89/0x29e0 kernel/exit.c:823 do_group_exit+0x125/0x310 kernel/exit.c:920 get_signal+0x3ec/0x2010 kernel/signal.c:2770 arch_do_signal_or_restart+0x2a8/0x1eb0 arch/x86/kernel/signal.c:811 handle_signal_work kernel/entry/common.c:144 [inline] exit_to_user_mode_loop kernel/entry/common.c:168 [inline] exit_to_user_mode_prepare+0x124/0x200 kernel/entry/common.c:198 syscall_exit_to_user_mode+0x36/0x260 kernel/entry/common.c:275 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x44ea59 Code: Unable to access opcode bytes at RIP 0x44ea2f. RSP: 002b:00007fd1200f3d98 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: 0000000000012255 RBX: 00000000006e6a18 RCX: 000000000044ea59 RDX: 00000001000001bd RSI: 00000000200001c0 RDI: 0000000000000003 RBP: 00000000006e6a10 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006e6a1c R13: 3030303030303030 R14: 3030303030303d65 R15: 2b74d0dd4a6f722c --- 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 syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches