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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AD29CC2BD09 for ; Fri, 28 Jun 2024 21:30:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type:To:From:Subject :Message-ID:Date:MIME-Version:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Owner; bh=ZIWtAA8Xev+5bClis/Hf4jpkqXQp3+VOHFxeEf/6JzU=; b=ZSyJSX8+p73fak7t2dstRJXU+6 NtgpNlxsQXovw/TZGrCC1YQWxILWd9RaMHb1Ao2SOJPtvdMjs+gOmYHl4YaIADcOKczH1vcPgHIhr pQRiqwGgvLU93iW6xhBJpdGTnRT2JsiakyeQzUJb5HMvp+O0qZYmQ2+wNivNBWWPJWFmMHlNwHa58 6vmYgaHYAQttOJlO7VMxOpKMMxHQpGVjCyEK3c6DHY+wzI9m1YHmRV1vTuU2UqOreTrCknFdxp4/o h+IrfInshnP0wEWuVPpiDbD9LTVRnG1i80x/1JR6GegOGBUWrxHNdGtj/1kk7/erhCgoec4DOhjGn fmKnwwGg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sNJB0-0000000F1eU-3V70; Fri, 28 Jun 2024 21:30:38 +0000 Received: from mail-io1-f78.google.com ([209.85.166.78]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sNJAq-0000000F1c5-23DW for linux-arm-kernel@lists.infradead.org; Fri, 28 Jun 2024 21:30:29 +0000 Received: by mail-io1-f78.google.com with SMTP id ca18e2360f4ac-7f3c8b1fee1so112865039f.0 for ; Fri, 28 Jun 2024 14:30:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719610226; x=1720215026; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ZIWtAA8Xev+5bClis/Hf4jpkqXQp3+VOHFxeEf/6JzU=; b=dNwA1E67pzjoiEdtP20O8uelLl4pZEuXm/X0WVqkVQ+vIqH2L8PVOxgRziCbFnk4Sw Lp9OsTIBI7bbEom0322WpO9ysk1b/0lvoJ3rDwHP+E4j89jGL8DAi8fj7087Ax+Hdwwz +vpn1Xmte7vYSnk2nxRnTIbvfesx5599xgTBQjvnzTl7aeVwyE7Vqvq3kbXo+IssKKkh bquiAhU429yHFSvgGbWc3BUyhlUWDXdK3TEBxVoNd18d1oX8P+wpdWtl4gQatSfCOmKj d1admGGhXaHAoqfuRx2LtoI3ToC3Ew4k7AKlT1dy74GpJb1wn3k4sX3HHRKIXXH3u/6U KZbQ== X-Forwarded-Encrypted: i=1; AJvYcCWOwu46SWwRJ+0rPs4ewFCVV5/XwiW0p9VlYubJaixliY7TWvp2UzuWcrhk78TiUIvFtYEX7wkksj3/oe81Fjv0t6Ch8ZGK+fEKRGplNBKaGz/GGAo= X-Gm-Message-State: AOJu0Yx0xFMZynIqgNTOd33+9CX5wqUh6bOb97Y0JNWJRKZEaZVy+yHd +0ZIqNZ3luQqnTKRClet5e2yBu5CRFBIUDJbrZLzis6ooFHgfDYevl41PM7Wkd789A/EtQaj0xC 7K4YZpbgJldFWnuybDySG1x8Ww+Olo6p2Lwoj3NqJtWyGHcTi4OMlM9o= X-Google-Smtp-Source: AGHT+IFStlaJ8hJVe0K/frourUyfzn+cX0J0cnxBAZeFPS3W4x7chDciA/ipEVYiBQj1qIo5cdy9BEElGvU17a3PF7QXrs61lSoG MIME-Version: 1.0 X-Received: by 2002:a05:6638:8420:b0:4b9:26f5:3632 with SMTP id 8926c6da1cb9f-4b9ecf452e0mr956895173.6.1719610226654; Fri, 28 Jun 2024 14:30:26 -0700 (PDT) Date: Fri, 28 Jun 2024 14:30:26 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000b6533c061bf9f4ff@google.com> Subject: [syzbot] [kernel?] upstream-arm64 test error: INFO: task hung in prepare_namespace From: syzbot To: catalin.marinas@arm.com, gregkh@linuxfoundation.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, rafael@kernel.org, syzkaller-bugs@googlegroups.com, will@kernel.org Content-Type: text/plain; charset="UTF-8" X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240628_143028_550240_93206B48 X-CRM114-Status: UNSURE ( 6.74 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello, syzbot found the following issue on: HEAD commit: 59ed70ca3c29 Merge remote-tracking branch 'tglx/devmsi-arm.. git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=17daa881980000 kernel config: https://syzkaller.appspot.com/x/.config?x=4e37fbf116261f0b dashboard link: https://syzkaller.appspot.com/bug?extid=b2e8737f75941acc4220 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm64 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/60815a10a042/disk-59ed70ca.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/ed29e6661847/vmlinux-59ed70ca.xz kernel image: https://storage.googleapis.com/syzbot-assets/0bc74b03961e/Image-59ed70ca.gz.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+b2e8737f75941acc4220@syzkaller.appspotmail.com INFO: task swapper/0:1 blocked for more than 143 seconds. Not tainted 6.10.0-rc5-syzkaller-g59ed70ca3c29 #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:swapper/0 state:D stack:0 pid:1 tgid:1 ppid:0 flags:0x0000000c Call trace: __switch_to+0x314/0x560 arch/arm64/kernel/process.c:553 context_switch kernel/sched/core.c:5408 [inline] __schedule+0x14ac/0x24d8 kernel/sched/core.c:6745 __schedule_loop kernel/sched/core.c:6822 [inline] schedule+0xbc/0x238 kernel/sched/core.c:6837 wait_for_device_probe+0x120/0x1c0 drivers/base/dd.c:772 prepare_namespace+0x5c/0x11c init/do_mounts.c:479 kernel_init_freeable+0x360/0x478 init/main.c:1591 kernel_init+0x24/0x2a0 init/main.c:1467 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860 Showing all locks held in the system: 1 lock held by khungtaskd/31: #0: ffff80008f3879e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:328 2 locks held by kworker/u8:2/42: #0: ffff0000c0031148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x624/0x15b8 kernel/workqueue.c:3205 #1: ffff800095677c20 ((work_completion)(&(&kfence_timer)->work)){+.+.}-{0:0}, at: process_one_work+0x6a0/0x15b8 kernel/workqueue.c:3205 3 locks held by kworker/u8:4/210: #0: ffff0000c181d148 ((wq_completion)async){+.+.}-{0:0}, at: process_one_work+0x624/0x15b8 kernel/workqueue.c:3205 #1: ffff800098157c20 ((work_completion)(&entry->work)){+.+.}-{0:0}, at: process_one_work+0x6a0/0x15b8 kernel/workqueue.c:3205 #2: ffff0000c2b941b0 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:1009 [inline] #2: ffff0000c2b941b0 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1093 [inline] #2: ffff0000c2b941b0 (&dev->mutex){....}-{3:3}, at: __driver_attach_async_helper+0xc8/0x230 drivers/base/dd.c:1143 1 lock held by hwrng/1371: #0: ffff800090aef948 (reading_mutex){+.+.}-{3:3}, at: hwrng_fillfn+0x6c/0x2b4 drivers/char/hw_random/core.c:495 ============================================= --- 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. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup