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 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 89226C47082 for ; Wed, 26 May 2021 15:44:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 62473613D3 for ; Wed, 26 May 2021 15:44:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233352AbhEZPpu (ORCPT ); Wed, 26 May 2021 11:45:50 -0400 Received: from mail-io1-f70.google.com ([209.85.166.70]:56223 "EHLO mail-io1-f70.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232537AbhEZPpu (ORCPT ); Wed, 26 May 2021 11:45:50 -0400 Received: by mail-io1-f70.google.com with SMTP id p2-20020a5d98420000b029043b3600ac76so976710ios.22 for ; Wed, 26 May 2021 08:44:18 -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=OdL20YqkAI7JJ2Wurl0dYHvUrhMz0DHPO3AdkhEoqS8=; b=ogAl729yblFEQvSwzrp+UIh8nxv/mBPaqCUSR3iI4YRgfUf5g+teLwZXouP0dV/RqH VFo0uMYj/J0HGhf5uEfhzwT3E9aGoEznWrZOS2wGdvtbcsqJxlbQiucpDV0eERTN8WOv Qf9vAQcUM/M3sCByQyjdj/omut7qiDGbxfB1/wu9C4vSbUgg9X73NoKnW1n0Ia2OrpxD RrlWQwWSH6dYLEJcmXkS22BPrLdTkmO6m5GgJZrem/ggGmlsUymytDAxa4uZ3Q3XGrro /krxb2SAnYhkiOY6wQuB1uHxszIvueLc0kwpHSq1DA5SYDLMFvSFg6rIzg9eIx+SUzvv zSnA== X-Gm-Message-State: AOAM533qwYbmYLO3UXrxruaUB09trxUfufvvIXGmKpyeMMXtHrzgIOqN wGFjxGmLv4w/rO2BoKNeBHv3A8gFnIKk0qeD3AJzA+bT+sEY X-Google-Smtp-Source: ABdhPJwg4V/nF+IW2KqtAB+SxTtb5cqxHI95UE+eQMXQMSI9dkKSicoQOTTt0voPm8eOjbAZCCPIWP6tVVmS/NzPyGjNGw36LDAF MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1ba7:: with SMTP id n7mr22093360ili.159.1622043858212; Wed, 26 May 2021 08:44:18 -0700 (PDT) Date: Wed, 26 May 2021 08:44:18 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000fa9f7005c33d83b9@google.com> Subject: [syzbot] KCSAN: data-race in __io_uring_cancel / io_uring_try_cancel_requests From: syzbot To: asml.silence@gmail.com, axboe@kernel.dk, io-uring@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: a050a6d2 Merge tag 'perf-tools-fixes-for-v5.13-2021-05-24'.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13205087d00000 kernel config: https://syzkaller.appspot.com/x/.config?x=3bcc8a6b51ef8094 dashboard link: https://syzkaller.appspot.com/bug?extid=73554e2258b7b8bf0bbf 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+73554e2258b7b8bf0bbf@syzkaller.appspotmail.com ================================================================== BUG: KCSAN: data-race in __io_uring_cancel / io_uring_try_cancel_requests write to 0xffff88811d8df330 of 8 bytes by task 3709 on cpu 1: io_uring_clean_tctx fs/io_uring.c:9042 [inline] __io_uring_cancel+0x261/0x3b0 fs/io_uring.c:9136 io_uring_files_cancel include/linux/io_uring.h:16 [inline] do_exit+0x185/0x1560 kernel/exit.c:781 do_group_exit+0xce/0x1a0 kernel/exit.c:923 get_signal+0xfc3/0x1610 kernel/signal.c:2835 arch_do_signal_or_restart+0x2a/0x220 arch/x86/kernel/signal.c:789 handle_signal_work kernel/entry/common.c:147 [inline] exit_to_user_mode_loop kernel/entry/common.c:171 [inline] exit_to_user_mode_prepare+0x109/0x190 kernel/entry/common.c:208 __syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline] syscall_exit_to_user_mode+0x20/0x40 kernel/entry/common.c:301 do_syscall_64+0x56/0x90 arch/x86/entry/common.c:57 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88811d8df330 of 8 bytes by task 6412 on cpu 0: io_uring_try_cancel_iowq fs/io_uring.c:8911 [inline] io_uring_try_cancel_requests+0x1ce/0x8e0 fs/io_uring.c:8933 io_ring_exit_work+0x7c/0x1110 fs/io_uring.c:8736 process_one_work+0x3e9/0x8f0 kernel/workqueue.c:2276 worker_thread+0x636/0xae0 kernel/workqueue.c:2422 kthread+0x1d0/0x1f0 kernel/kthread.c:313 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294 Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 6412 Comm: kworker/u4:9 Not tainted 5.13.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events_unbound io_ring_exit_work ================================================================== --- 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.