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 0C383C11F66 for ; Mon, 12 Jul 2021 16:09:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E805A61248 for ; Mon, 12 Jul 2021 16:09:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231868AbhGLQMT (ORCPT ); Mon, 12 Jul 2021 12:12:19 -0400 Received: from mail-il1-f199.google.com ([209.85.166.199]:43549 "EHLO mail-il1-f199.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231651AbhGLQMQ (ORCPT ); Mon, 12 Jul 2021 12:12:16 -0400 Received: by mail-il1-f199.google.com with SMTP id e16-20020a056e0204b0b029020c886c9370so2574051ils.10 for ; Mon, 12 Jul 2021 09:09:28 -0700 (PDT) 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=vJplYivQzcGWjNSabykUkuqB126rvR4luN1jl8jmks8=; b=L+LeTWuW3jagDs3HmZJ6G/xdjo9Ul5RFhDumF3ptTZUWtSj2D/nieNE364bjQWERBM XpdIM0BtWHOf4L6phbS1QYsJ/S6jBS4eSqlwdjep8ozGqqK10jiosgpGtCUiaxXfe6Q7 Xwf0SiJgRcKND41Rs5MboUL1uzi1IBGLtH596rkJ3z1+PQ/1Ca1RTKlqr0FP/vFmy1id EHwGM8vUOsNJcy1dGOCMExpcqodkFrxsFj9Lmm7Lc8N5waFx1CupjmLIx+ULbtsVMGuP pYZgRoSZfL2GzzsgaLtBXLFgHy48I6p3mV7eCdOcIeJWxD2wyLlCymc0eehXUciILJrj uR4A== X-Gm-Message-State: AOAM530G2+idk3lHq914oW8Gcerbp7RXQFiL5L3OnbTL/oiXDD9PnKgQ 2StnXWiDUl15cf+vU5GOPSyKXE61Dqh7omqFMk9FVL/WjdP6 X-Google-Smtp-Source: ABdhPJxALuS94+Q/I/hiCV+3ZiAT2NU4QR0ESCCCi5V6qrcsqwXFD7dVEBUny3mN3H9f5y3ngY6F30zDOHN1pBzx2bis+6HOFVF6 MIME-Version: 1.0 X-Received: by 2002:a92:6f0a:: with SMTP id k10mr37377927ilc.105.1626106167835; Mon, 12 Jul 2021 09:09:27 -0700 (PDT) Date: Mon, 12 Jul 2021 09:09:27 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000080403805c6ef586d@google.com> Subject: [syzbot] KCSAN: data-race in call_rcu / rcu_gp_kthread From: syzbot To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk 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: e73f0f0e Linux 5.14-rc1 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=172196d2300000 kernel config: https://syzkaller.appspot.com/x/.config?x=f5e73542d774430b dashboard link: https://syzkaller.appspot.com/bug?extid=e08a83a1940ec3846cd5 compiler: Debian clang version 11.0.1-2 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+e08a83a1940ec3846cd5@syzkaller.appspotmail.com ================================================================== BUG: KCSAN: data-race in call_rcu / rcu_gp_kthread write to 0xffffffff837328a0 of 8 bytes by task 11 on cpu 0: rcu_gp_fqs kernel/rcu/tree.c:1949 [inline] rcu_gp_fqs_loop kernel/rcu/tree.c:2010 [inline] rcu_gp_kthread+0xd78/0xec0 kernel/rcu/tree.c:2169 kthread+0x262/0x280 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 read to 0xffffffff837328a0 of 8 bytes by task 30193 on cpu 1: __call_rcu_core kernel/rcu/tree.c:2946 [inline] __call_rcu kernel/rcu/tree.c:3062 [inline] call_rcu+0x4b0/0x6c0 kernel/rcu/tree.c:3109 file_free fs/file_table.c:58 [inline] __fput+0x43e/0x4e0 fs/file_table.c:298 ____fput+0x11/0x20 fs/file_table.c:313 task_work_run+0xae/0x130 kernel/task_work.c:164 get_signal+0x156c/0x15e0 kernel/signal.c:2581 arch_do_signal_or_restart+0x2a/0x220 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+0x109/0x190 kernel/entry/common.c:209 __syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline] syscall_exit_to_user_mode+0x20/0x40 kernel/entry/common.c:302 do_syscall_64+0x49/0x90 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0x0000000000000f57 -> 0x0000000000000f58 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 30193 Comm: syz-executor.5 Tainted: G W 5.14.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 ================================================================== --- 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.