From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CA0F777F10 for ; Wed, 6 Mar 2024 10:57:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.69 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709722641; cv=none; b=cECwDUn51E9EgHEQxD/b4xvcIwnGGiaJGjqGvMPdy2FcZT9I/2GZl9NimgvZF7zL08/TJUDDq8nMg0lrY3DugSigeZRFZV9n+uSpYeDzbnfAS2eWvoBRXHa9kN6FnzkiYinycCLu9DpQWIUXmToCSj0tY4Sb1cH2BsE5W01kLXQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709722641; c=relaxed/simple; bh=NcwDt28WD1YEa1pUSgc8ylFJjluAMhWyX8PCK+tuF6k=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=OBy5gE+QyN2Gek1oqY/1bpSIkhDJN98C24nb4Vo0sGzPNe2FI4Q6kk+TmTmU14rRVm3m0PuV9lznLRUxNdeDWcqJwdLkfY7Ih4O5sBcUlxL3jtpZBdUdFIO8ibCZRkHLFUoL+JjsUAaDbd6RZ15m7KhigqTYH4qBXMUec/mvF98= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.69 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-io1-f69.google.com with SMTP id ca18e2360f4ac-7c83b729ba5so78799639f.0 for ; Wed, 06 Mar 2024 02:57:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709722639; x=1710327439; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=8qXxCetncWmf0GqFMx7p5lJmRGpeOCkuynw+Qj5Z8c0=; b=sHiu8j0TGrQKYX0Ovu8luhpnCbh52xon7QcfHG4CNVIC7AMXPoM5Ew5jkXYy6IQ60E UnalczFSvsA+zz6lTL7dgV+vFQDHL8SVIz8DDr3j8cilHy5GzbiI5YGKrvA9e3s+1sQX ZGVvWMR0baU1e5m/U/JC2ogEzrgpd5VLaJh/Ya48r+0KV4aeMOkA8PiAYgVbggt+1lYI qcVJ4UBXhaDVMfztcTvIclXTy65ZW5zyhCrp6GzbbcLM7NRwGec9PNIhhWdH+u50+1Q8 6LrKmcD6lUTM+w2GCrFUYGipCa+AgNRZIvdAuKlbCEb8HeKkqZwYIag2DXvtSCQ77SNa lWrw== X-Forwarded-Encrypted: i=1; AJvYcCUqK48+ZrWD14szgp+xanKkqdVjKZHGEvltqPyFXhua/x9ybLA+JnWpmprZkdLYTEozleUsV/8jOzteRR84nMoh2Wozq7/MJy+VidPQ X-Gm-Message-State: AOJu0YwqDxaAtyINiiC7J8bd83zHMFL8oMbLvRM7oZIUql6XORfWd5Kn Juas3B6cWSxDbhwbdK0Y3fNEFoJEAPnkbiY5j+7X8v8Forhu44KwrGK2VQ8dZPVwEIWSK7P72GC 71cUii+I/R+hB72CBkGRo3IkC7Fk1fcVYkOgIIoG0caFv8Dn/uTLlR+E= X-Google-Smtp-Source: AGHT+IH6YLEGFgRiGIyEjvD7BFJjeOW+RjgB6wkTjfNiPoIvfnN6/JBkaHbXIRzGSOOU+E5tyT9m6Q7Yz4Hx6VF9w13dlbTQP5tN Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6638:3784:b0:474:d7bf:64ed with SMTP id w4-20020a056638378400b00474d7bf64edmr706584jal.6.1709722639017; Wed, 06 Mar 2024 02:57:19 -0800 (PST) Date: Wed, 06 Mar 2024 02:57:19 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000009033c40612fbd20f@google.com> Subject: [syzbot] [jfs?] INFO: task hung in __get_metapage (2) From: syzbot To: jfs-discussion@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, shaggy@kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 9910665503b3 Merge branch 'for-next/core' into for-kernelci 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=12413316180000 kernel config: https://syzkaller.appspot.com/x/.config?x=2402d46ab3c7e581 dashboard link: https://syzkaller.appspot.com/bug?extid=72feb48a17265d9bf496 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=129fb526180000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12c40bba180000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/16059f53446c/disk-99106655.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/7fc6c7c495d5/vmlinux-99106655.xz kernel image: https://storage.googleapis.com/syzbot-assets/d8b0ce53ea33/Image-99106655.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/1d3700eeba9f/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+72feb48a17265d9bf496@syzkaller.appspotmail.com INFO: task jfsCommit:94 blocked for more than 143 seconds. Not tainted 6.8.0-rc6-syzkaller-g9910665503b3 #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:jfsCommit state:D stack:0 pid:94 tgid:94 ppid:2 flags:0x00000008 Call trace: __switch_to+0x314/0x560 arch/arm64/kernel/process.c:553 context_switch kernel/sched/core.c:5400 [inline] __schedule+0x1498/0x24b4 kernel/sched/core.c:6727 __schedule_loop kernel/sched/core.c:6802 [inline] schedule+0xb8/0x19c kernel/sched/core.c:6817 io_schedule+0x8c/0x12c kernel/sched/core.c:9023 __lock_metapage+0x1cc/0x458 fs/jfs/jfs_metapage.c:50 lock_metapage fs/jfs/jfs_metapage.c:64 [inline] __get_metapage+0x96c/0x1050 fs/jfs/jfs_metapage.c:639 diIAGRead+0xe4/0x14c fs/jfs/jfs_imap.c:2669 diFree+0x800/0x2648 fs/jfs/jfs_imap.c:956 jfs_evict_inode+0x2d0/0x3f4 fs/jfs/inode.c:156 evict+0x260/0x68c fs/inode.c:665 iput_final fs/inode.c:1739 [inline] iput+0x734/0x818 fs/inode.c:1765 txUpdateMap+0x73c/0x8e4 fs/jfs/jfs_txnmgr.c:2367 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline] jfs_lazycommit+0x3a4/0x98c fs/jfs/jfs_txnmgr.c:2733 kthread+0x288/0x310 kernel/kthread.c:388 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860 Showing all locks held in the system: 1 lock held by khungtaskd/29: #0: ffff80008ee73f40 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:297 2 locks held by jfsCommit/94: #0: ffff0000d8558920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2cc/0x2648 fs/jfs/jfs_imap.c:886 #1: ffff0000ddd3a638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2e0/0x2648 fs/jfs/jfs_imap.c:891 2 locks held by getty/5932: #0: ffff0000d35540a0 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340 #1: ffff800094f722f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41c/0x1228 drivers/tty/n_tty.c:2201 3 locks held by syz-executor149/7710: ============================================= --- 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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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