From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DEC3FC433F5 for ; Fri, 17 Sep 2021 07:45:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C4D1B61164 for ; Fri, 17 Sep 2021 07:45:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240112AbhIQHqv (ORCPT ); Fri, 17 Sep 2021 03:46:51 -0400 Received: from mail-il1-f197.google.com ([209.85.166.197]:39736 "EHLO mail-il1-f197.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235911AbhIQHqu (ORCPT ); Fri, 17 Sep 2021 03:46:50 -0400 Received: by mail-il1-f197.google.com with SMTP id x7-20020a920607000000b002302afca41bso20411942ilg.6 for ; Fri, 17 Sep 2021 00:45:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=qhsP2+cq+V34wONR8zohN2S7Vy1bYXDChrogQdy+HvA=; b=jsoSOGQoFZUDoy+2x59RG35mqYhdM8e0cbHG2qt7DbyfdwAYSJZr05Z162CylwEd0x 7QLd4xPRFpa9t2/v6jkgemAfSPTE7aMsVxfS23m4G17//doVdAj3povB1NAeVoJ/cDCI /bY5HcYfixBAhpUotSRjoTfhVXfIwbg1UcTczuBjBwIhTYSdQ8bVdXvVno7/UIlJVAEu AvA70/3zrCnthK+lsurOU3W41RORu7LqXYe/3X6eIm/MTFaZcJ9Jwc1v5ZOdDLKn3CvP L7H94iOA1yJizYC6kT9EMKLm3QH9K591NVEgb+5Q8AFYcWh59sKtcFW9L2/GT7i1Kw4J NdoA== X-Gm-Message-State: AOAM533a0kEHgZbZ7fnOVV9D8Behtv9XsdFRImRdbRwM4nG+ERTDql+N K5ooNCmWS+75Hs8edXmiIeXgb8If4T81px5mAXetFHTHQm1y X-Google-Smtp-Source: ABdhPJywQVM7bxgbMCGlFyaonYOt0+ZCdP7tNTOdXECGnpyCU0GwOMHdIoVIDu3qUEC0nK51gAqa/tgUBlfFad8m/JpmqbuGYIqf MIME-Version: 1.0 X-Received: by 2002:a05:6602:2c05:: with SMTP id w5mr7752796iov.160.1631864728261; Fri, 17 Sep 2021 00:45:28 -0700 (PDT) Date: Fri, 17 Sep 2021 00:45:28 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000073194a05cc2c1db6@google.com> Subject: [syzbot] WARNING: refcount bug in nr_release (2) From: syzbot To: davem@davemloft.net, kuba@kernel.org, linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, ralf@linux-mips.org, 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: c1b13fe76e95 Add linux-next specific files for 20210901 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1564c986300000 kernel config: https://syzkaller.appspot.com/x/.config?x=e2afff7bc32736e5 dashboard link: https://syzkaller.appspot.com/bug?extid=053c8d94c7f45da6e6c8 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1 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+053c8d94c7f45da6e6c8@syzkaller.appspotmail.com ------------[ cut here ]------------ refcount_t: saturated; leaking memory. WARNING: CPU: 0 PID: 2068 at lib/refcount.c:22 refcount_warn_saturate+0x12d/0x1e0 lib/refcount.c:22 Modules linked in: CPU: 0 PID: 2068 Comm: syz-executor.3 Not tainted 5.14.0-next-20210901-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:refcount_warn_saturate+0x12d/0x1e0 lib/refcount.c:22 Code: 09 31 ff 89 de e8 f3 98 9e fd 84 db 0f 85 72 ff ff ff e8 a6 92 9e fd 48 c7 c7 60 00 e4 89 c6 05 62 76 82 09 01 e8 60 89 18 05 <0f> 0b e9 53 ff ff ff e8 87 92 9e fd 0f b6 1d 49 76 82 09 31 ff 89 RSP: 0018:ffffc9000dd9fa78 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff888095d91c80 RSI: ffffffff815dba38 RDI: fffff52001bb3f41 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815d581e R11: 0000000000000000 R12: ffff88803f939200 R13: ffff8880a961a080 R14: ffff88803f939218 R15: ffff888011eccaa0 FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f66614c8070 CR3: 00000000198d8000 CR4: 00000000001526f0 Call Trace: __refcount_add include/linux/refcount.h:201 [inline] __refcount_inc include/linux/refcount.h:250 [inline] refcount_inc include/linux/refcount.h:267 [inline] sock_hold include/net/sock.h:702 [inline] nr_release+0x3ba/0x450 net/netrom/af_netrom.c:520 __sock_release+0xcd/0x280 net/socket.c:649 sock_close+0x18/0x20 net/socket.c:1314 __fput+0x288/0x9f0 fs/file_table.c:280 task_work_run+0xdd/0x1a0 kernel/task_work.c:164 exit_task_work include/linux/task_work.h:32 [inline] do_exit+0xbae/0x2a30 kernel/exit.c:825 do_group_exit+0x125/0x310 kernel/exit.c:922 get_signal+0x47f/0x2160 kernel/signal.c:2868 arch_do_signal_or_restart+0x2a9/0x1c40 arch/x86/kernel/signal.c:865 handle_signal_work kernel/entry/common.c:148 [inline] exit_to_user_mode_loop kernel/entry/common.c:172 [inline] exit_to_user_mode_prepare+0x17d/0x290 kernel/entry/common.c:209 __syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline] syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:302 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x4665f9 Code: Unable to access opcode bytes at RIP 0x4665cf. RSP: 002b:00007f1282a60218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca RAX: fffffffffffffe00 RBX: 000000000056bf88 RCX: 00000000004665f9 RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000056bf88 RBP: 000000000056bf80 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf8c R13: 00007fffbb91b31f R14: 00007f1282a60300 R15: 0000000000022000 --- 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.