From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f69.google.com (mail-oo1-f69.google.com [209.85.161.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 D8C5A63CB for ; Sat, 14 Feb 2026 16:16:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.69 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771085783; cv=none; b=fGaRm8ARZ7GzVuIKgWcKD3qYGAbbLRU+/J4FQvdQszmwOBOgq4RxKYbfnDElDDVibPZlM7sQY/p913f3FrboUZKobdAQEaHHEGS7NLOEMenSK3HrHIcJ2+T7VwXCNM0d+frnid0I6d+CAGB+Y97xWirvRONGJB3709WfDEEt4lc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771085783; c=relaxed/simple; bh=elzy4/ZV1w/GLO/O9z1s+8xprAPmvhZugMtYF3bDk9s=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=YRZLXuYXutcSzvz3yMft/EZtIEzArdw3VT3wXIU+YWKB1P/eTtWYZzF9ZEnoKfz9/Gm6bBdQlFmYPW4VDwxtqXrnP3IyXDOnOwYGoPXyapJP5or3HFUyYI0lioH7Ek9t0o8rbP0mEkpfCt4tZFfvD1iM/Wvle6N5on/UtlIHhhU= 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.161.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-oo1-f69.google.com with SMTP id 006d021491bc7-66308f16ea0so18808419eaf.0 for ; Sat, 14 Feb 2026 08:16:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771085781; x=1771690581; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=I4FjZ2bSbR+2D3ZyxFNPtgml20S636oIMmwTRfcYzXo=; b=EnJ+Dk0182Z5CzL/ppBex+A1advH9FvZN1K1GjsURYaT0A83RulLkzhkT88lzkf/8d 197N3q86MDSpdFqR/WlTFywfuhoVyQwlXPh10L8dMD4cSX7F9ptfKvv+g4z1JaGPW5zy tQ8SI5WtnjZ6Q4WSwwQ02JPkP/X7y2Jzo6FJjLEKVfGU+ynMGlWjW9Chln+AuA9k66qP OD+G4dbcW4S/0n+P4cJOviBHVa/LmwmgiO48bMFL7DIZo3FjQkeY3NWCcw2bQfnM+gfh ihT1mwi0dI6irLJwuxtmntJvf9qnmkpFdRgVvU5NGD2heNRA9BtkSkh6r5YEtw5xPkNS R6hQ== X-Gm-Message-State: AOJu0YyJ6fsPiQqAjZx5q+ZIXRna7HfJXkS/vK4A28goCbdAcJpyLYNq GQ4evoZwzPngwZMvJCvxNxW7HN0B2Ne+Bi7toneufNKFyBf4JolLB5i35AUCobmYL/3IJhd7KAe ZWTCg9YWJ13/UcNZNYmR9h2EAbKgMUiWBwPXcds0OPTmd3JCxrskZHrWItTc= 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:6820:480c:b0:679:4e8d:2e67 with SMTP id 006d021491bc7-6794e8d31aamr389563eaf.22.1771085780782; Sat, 14 Feb 2026 08:16:20 -0800 (PST) Date: Sat, 14 Feb 2026 08:16:20 -0800 In-Reply-To: <699000b2.050a0220.3a4a67.00a6.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69909fd4.a70a0220.2c38d7.00d0.GAE@google.com> Subject: Forwarded: Re: [syzbot] [xfs?] inconsistent lock state in igrab From: syzbot To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com. *** Subject: Re: [syzbot] [xfs?] inconsistent lock state in igrab Author: djwong@kernel.org #syz test git://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git f90fa6ef5701f63c5ed29d93b6d58a2fde30836d On Sat, Feb 14, 2026 at 12:18:36AM -0800, syzbot wrote: > syzbot has found a reproducer for the following issue on: > > HEAD commit: cd7a5651db26 alpha: add missing address argument in call t.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=13b47e5a580000 > kernel config: https://syzkaller.appspot.com/x/.config?x=e600149b13c010eb > dashboard link: https://syzkaller.appspot.com/bug?extid=5eb0d61dfb76ca12670c > compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15df8722580000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17f362aa580000 > > Downloadable assets: > disk image: https://storage.googleapis.com/syzbot-assets/ea46ed04f19d/disk-cd7a5651.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/ee7aa4ba7700/vmlinux-cd7a5651.xz > kernel image: https://storage.googleapis.com/syzbot-assets/70280d10edbe/bzImage-cd7a5651.xz > mounted in repro: https://storage.googleapis.com/syzbot-assets/41cb64e4f612/mount_0.gz > fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1105a6e6580000) > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+5eb0d61dfb76ca12670c@syzkaller.appspotmail.com > > I/O error, dev loop0, sector 512 op 0x0:(READ) flags 0x880700 phys_seg 1 prio class 2 > I/O error, dev loop0, sector 18692 op 0x0:(READ) flags 0x880700 phys_seg 1 prio class 2 > ================================ > WARNING: inconsistent lock state > syzkaller #0 Not tainted > -------------------------------- > inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage. > ksoftirqd/0/15 [HC0[0]:SC1[1]:HE1:SE0] takes: > ffff888059619180 (&sb->s_type->i_lock_key#36){+.?.}-{3:3}, at: spin_lock include/linux/spinlock.h:341 [inline] > ffff888059619180 (&sb->s_type->i_lock_key#36){+.?.}-{3:3}, at: igrab+0x2a/0x230 fs/inode.c:1583 > {SOFTIRQ-ON-W} state was registered at: > lock_acquire kernel/locking/lockdep.c:5868 [inline] > lock_acquire+0x17c/0x330 kernel/locking/lockdep.c:5825 > __raw_spin_lock include/linux/spinlock_api_smp.h:158 [inline] > _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154 > spin_lock include/linux/spinlock.h:341 [inline] > unlock_new_inode+0x7a/0x330 fs/inode.c:1222 > xfs_finish_inode_setup fs/xfs/xfs_inode.h:630 [inline] > xfs_setup_existing_inode fs/xfs/xfs_inode.h:637 [inline] > xfs_iget+0x1196/0x30f0 fs/xfs/xfs_icache.c:814 > xfs_mountfs+0x108c/0x20b0 fs/xfs/xfs_mount.c:1072 > xfs_fs_fill_super+0x153f/0x1f20 fs/xfs/xfs_super.c:1938 > get_tree_bdev_flags+0x38c/0x620 fs/super.c:1694 > vfs_get_tree+0x92/0x320 fs/super.c:1754 > fc_mount fs/namespace.c:1193 [inline] > do_new_mount_fc fs/namespace.c:3760 [inline] > do_new_mount fs/namespace.c:3836 [inline] > path_mount+0x7d0/0x23d0 fs/namespace.c:4146 > do_mount fs/namespace.c:4159 [inline] > __do_sys_mount fs/namespace.c:4348 [inline] > __se_sys_mount fs/namespace.c:4325 [inline] > __x64_sys_mount+0x293/0x310 fs/namespace.c:4325 > do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] > do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94 > entry_SYSCALL_64_after_hwframe+0x77/0x7f > irq event stamp: 972992 > hardirqs last enabled at (972992): [] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:178 [inline] > hardirqs last enabled at (972992): [] _raw_spin_unlock_irqrestore+0x52/0x80 kernel/locking/spinlock.c:194 > hardirqs last disabled at (972991): [] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:130 [inline] > hardirqs last disabled at (972991): [] _raw_spin_lock_irqsave+0x52/0x60 kernel/locking/spinlock.c:162 > softirqs last enabled at (972968): [] run_ksoftirqd kernel/softirq.c:1063 [inline] > softirqs last enabled at (972968): [] run_ksoftirqd+0x38/0x60 kernel/softirq.c:1055 > softirqs last disabled at (972973): [] run_ksoftirqd kernel/softirq.c:1063 [inline] > softirqs last disabled at (972973): [] run_ksoftirqd+0x38/0x60 kernel/softirq.c:1055 > > other info that might help us debug this: > Possible unsafe locking scenario: > > CPU0 > ---- > lock(&sb->s_type->i_lock_key#36); > > lock(&sb->s_type->i_lock_key#36); > > *** DEADLOCK *** > > no locks held by ksoftirqd/0/15. > > stack backtrace: > CPU: 0 UID: 0 PID: 15 Comm: ksoftirqd/0 Not tainted syzkaller #0 PREEMPT(full) > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 > Call Trace: > > __dump_stack lib/dump_stack.c:94 [inline] > dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120 > print_usage_bug.part.0+0x257/0x340 kernel/locking/lockdep.c:4042 > print_usage_bug kernel/locking/lockdep.c:4010 [inline] > valid_state kernel/locking/lockdep.c:4056 [inline] > mark_lock_irq kernel/locking/lockdep.c:4267 [inline] > mark_lock+0x74a/0xa20 kernel/locking/lockdep.c:4753 > mark_usage kernel/locking/lockdep.c:4642 [inline] > __lock_acquire+0x103a/0x2630 kernel/locking/lockdep.c:5191 > lock_acquire kernel/locking/lockdep.c:5868 [inline] > lock_acquire+0x17c/0x330 kernel/locking/lockdep.c:5825 > __raw_spin_lock include/linux/spinlock_api_smp.h:158 [inline] > _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154 > spin_lock include/linux/spinlock.h:341 [inline] > igrab+0x2a/0x230 fs/inode.c:1583 > fserror_report+0x3fd/0x750 fs/fserror.c:159 > fserror_report_io include/linux/fserror.h:48 [inline] > iomap_finish_folio_read+0x168/0x2c0 fs/iomap/buffered-io.c:407 > iomap_read_end_io+0x11a/0x430 fs/iomap/bio.c:17 > bio_endio+0x755/0x8b0 block/bio.c:1790 > blk_update_request+0x741/0x1330 block/blk-mq.c:1016 > blk_mq_end_request+0x5b/0x420 block/blk-mq.c:1178 > lo_complete_rq+0x1d4/0x2a0 drivers/block/loop.c:314 > blk_complete_reqs+0xb1/0xf0 block/blk-mq.c:1253 > handle_softirqs+0x1ea/0x910 kernel/softirq.c:622 > run_ksoftirqd kernel/softirq.c:1063 [inline] > run_ksoftirqd+0x38/0x60 kernel/softirq.c:1055 > smpboot_thread_fn+0x3d3/0xaa0 kernel/smpboot.c:160 > kthread+0x370/0x450 kernel/kthread.c:467 > ret_from_fork+0x754/0xd80 arch/x86/kernel/process.c:158 > ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 > > > > --- > 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. >