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=ham 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 976ACC433C1 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 53B1A6195A for ; Mon, 29 Mar 2021 07:35:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230224AbhC2Hep (ORCPT ); Mon, 29 Mar 2021 03:34:45 -0400 Received: from mail-il1-f199.google.com ([209.85.166.199]:53790 "EHLO mail-il1-f199.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230052AbhC2HeT (ORCPT ); Mon, 29 Mar 2021 03:34:19 -0400 Received: by mail-il1-f199.google.com with SMTP id k12so1424978ilo.20 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=rkx6f5eZxM8bJf3bhoFtK8wtJFTPJJFa5t60FGLf0/Q=; b=sMpc5XwcwTb5j03VXhvdBViVj1Jq2cm4/kFwxVvtSLsJy9fgKhusWdh/B6rvZ+RfBU 08NhOkuwjQDRAHbqFCXWZbUtYxYGMW9FL5nDCZLzw39Jd18fJLdOb/fZ/SxZSU3Hk4nV HN1nnhl/dBI8lPg7hb1rpoXIx7rw9mWUZCY/zCZk14etmulyF9mUZQDzMQtlyiZwLA/C gSZG44EN7tA+fpVzlgaBjDE4Mv4X/nwT54Ax3EJHmr5EnCNmd8k9EutP7wDfhQrU+RVY 0aHKBDoxLD0Jg4Ih5s9f2h3tDdlvsZoTza5FlkVnzo1xkj8P3yt1QFu6W7ra2i1kzLBE n4gQ== X-Gm-Message-State: AOAM531zpLjUzwAVzgsxl6DXBwKBa/wJ5gIYt5bOcDr/7ZIOOx9dJ+SL cf3NZkEQ/vxEDDgtczp2QoPZ+xwR6Hwrl+xGVOwxuQ8dV+I8 X-Google-Smtp-Source: ABdhPJzYITpmri6/x2Ymkbatr4u8o4D5pL32ACoBzIVypQdBNjw4pvA13SQb2JFhAHLNwpjjb0JknvExUT5m3zQ5XAzWxMFfvIj0 MIME-Version: 1.0 X-Received: by 2002:a02:694b:: with SMTP id e72mr22964093jac.89.1617003258037; 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: <000000000000cbcdca05bea7e829@google.com> Subject: [syzbot] WARNING: still has locks held 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: io-uring@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=10fcce62d00000 kernel config: https://syzkaller.appspot.com/x/.config?x=d4e9addca54f3b44 dashboard link: https://syzkaller.appspot.com/bug?extid=796d767eb376810256f5 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17d06ddcd00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=150764bed00000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+796d767eb376810256f5@syzkaller.appspotmail.com ==================================== WARNING: iou-sqp-8386/8387 still has locks held! 5.12.0-rc4-syzkaller #0 Not tainted ------------------------------------ 1 lock held by iou-sqp-8386/8387: #0: ffff88801e1d2470 (&sqd->lock){+.+.}-{3:3}, at: io_sq_thread+0x24c/0x13a0 fs/io_uring.c:6731 stack backtrace: CPU: 1 PID: 8387 Comm: iou-sqp-8386 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 try_to_freeze include/linux/freezer.h:66 [inline] get_signal+0x171a/0x2150 kernel/signal.c:2576 io_sq_thread+0x8d2/0x13a0 fs/io_uring.c:6748 --- 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. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches