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=-8.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 CEC88C433E2 for ; Mon, 29 Mar 2021 07:35:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 99E966195E for ; Mon, 29 Mar 2021 07:35:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231151AbhC2Hep (ORCPT ); Mon, 29 Mar 2021 03:34:45 -0400 Received: from mail-il1-f198.google.com ([209.85.166.198]:38291 "EHLO mail-il1-f198.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230516AbhC2HeT (ORCPT ); Mon, 29 Mar 2021 03:34:19 -0400 Received: by mail-il1-f198.google.com with SMTP id o7so11258354ilt.5 for ; Mon, 29 Mar 2021 00:34: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=lBStvjRDQ5cgv9i64/xI95nXksjc9KFyRlQBs2TGHqI=; b=WfRsD0Wum89dcNIH0Sbelh45/5eQXLHXM2phBIe30z6oT7lQTMJq6+jhZihJbqx9r3 sRDCnbRM2jR4XREvs364jpnwxSVufE+1O3+HoEZTyh4vN2BOhS9H4LrzFlPYB4ujj59X yHn0tQanBuxO632Ic0ChwF+0/GF/LF+5nUI+c8xvbjMCon9C69/PwfN7bAyVLVIQcY9i 5d4nLGQ3MSr6AL9hOuyFrtPb1myDtL8N68hl8RQP3Gss4k4et3ZvcSEmh1BiiK+YbAoB xDfll19fK3Xs6aEefrAchidpsKK9slha//Yp4EGyU8OzCQRyoCzmCjqMCR1uffj2BLQt HSRw== X-Gm-Message-State: AOAM531v9MfHeOLErUKkA086AWIaA5fnXPZ0jAP68e1MZxF0UUSXQRaC gOzvb/b4lVUiDUNsc9mWW9gXiQjjwn2NeJpWLUx3AT5H38oj X-Google-Smtp-Source: ABdhPJySMKAh0t5qZNyTGzPjJ6vKcA86/lle9pjA3BOncntSeIqti786AppiH6+JKm8btWC9s4fDNnV10I801jQXkvV32DqMYugG MIME-Version: 1.0 X-Received: by 2002:a5e:990f:: with SMTP id t15mr12105880ioj.180.1617003258436; Mon, 29 Mar 2021 00:34:18 -0700 (PDT) Date: Mon, 29 Mar 2021 00:34:18 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000d1e19505bea7e8b8@google.com> Subject: [syzbot] WARNING: suspicious RCU usage in io_sq_thread 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: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 81b1d39f Merge tag '5.12-rc4-smb3' of git://git.samba.org/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=156f3d9ed00000 kernel config: https://syzkaller.appspot.com/x/.config?x=d4e9addca54f3b44 dashboard link: https://syzkaller.appspot.com/bug?extid=0cbf22e728582ade44f2 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+0cbf22e728582ade44f2@syzkaller.appspotmail.com WARNING: suspicious RCU usage 5.12.0-rc4-syzkaller #0 Not tainted ----------------------------- kernel/sched/core.c:8294 Illegal context switch in RCU-bh read-side critical section! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 0 1 lock held by iou-sqp-10136/10139: #0: ffff88801a5a8c70 (&sqd->lock){+.+.}-{3:3}, at: io_sq_thread+0xff2/0x13a0 fs/io_uring.c:6794 stack backtrace: CPU: 1 PID: 10139 Comm: iou-sqp-10136 Not tainted 5.12.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x141/0x1d7 lib/dump_stack.c:120 ___might_sleep+0x229/0x2c0 kernel/sched/core.c:8294 io_sq_thread+0xbae/0x13a0 fs/io_uring.c:6768 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294 --- 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.