From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f200.google.com (mail-oi1-f200.google.com [209.85.167.200]) (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 1B6DE2931E8 for ; Fri, 17 Jul 2026 04:39:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.200 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784263146; cv=none; b=a4LzJM9gbU2V8lr8elAD87UCloa2fylsP7OQf7db4A/1Ygze+uuCHP/OvgDuYbJ8BAloo/QnmyIs9FL6tZgLlUbQP/ft+KGR81n4Dxa6hMHlTQ3g0ZGP9sRP4nVA4RRx9MN9zfYfmwROUW8GZ1wR29CY3Rpnl4hGFBpVbTUBY9I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784263146; c=relaxed/simple; bh=AYp7AhoKIwEsPRJRyZAraQex/BbhgqLaBrDT2bMsht8=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=JzWKXjKiD4l3mywiu/gluYi5MSLyI/ciISHSad+OG+aKybIzxGQNfSFK5B/G+OddPmXjvG2q0yY9TLdWuODpqK1VY/kVso1S0repXuedNoSXtHwkryTonjQxL+2zxIrdV7SdVyZoeQWV8PS2hVo4kzaBwLJy7ckU/URYssfEZpU= 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.167.200 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-oi1-f200.google.com with SMTP id 5614622812f47-4a441e90050so1045218b6e.1 for ; Thu, 16 Jul 2026 21:39:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1784263144; x=1784867944; h=content-type:to:from:subject:message-id:in-reply-to:date :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to:content-type; bh=D+WEiGZCQRNnUL9BqiJKa9Pspmrp+3XysRvsX1UrLHs=; b=IJmkEHLlBwK0RaVPFTFZOowRxjdS991Aey1wUpFMRnrwnZHgdvwOw+RJpE4xV/ZwJK BXp8kyXSdgFGVnOaTYx/sgM4o3GL3J04w6MYHKM/mqh9Tm32gf8bd0DzLIFXL4+rjAt0 VtUBXNAMOtSdFXvpb3R8t4ga1iXVcBq7jsvA03B6zL6b4EKbgsJGb7Q+D9d/pEWqDRCP 525vvY8jvNcB9hJdUwIxGZmyQh4/5VMLSuUXDy7sbIOoIi41K46DR+rYyAdiXwFbLseb u08Oh0DViqQx+2VcwINKWepE/46X/m8YKU1uFxO1wdZULc73ePf60TLppYW4nkXA9Jdb kevw== X-Forwarded-Encrypted: i=1; AHgh+RpUbEvkdUxn+os9TEBxEH9GWlH/TIUrXaExnNBOQEvTe45N2+9VNFcVwQ8hraHK1XLzZ91cVmaE9AlKzI8=@vger.kernel.org X-Gm-Message-State: AOJu0YyJStMhFVT8nHTnvYkIpL9+utPUL/1rcdirPtEz/S4o5W8M0GLb 5+t0CC6OtRAz5XJWAi/2TohrtRjzu1pgzdVGS1KEHXrucVpbL7go7L/snz7EFC9yFnK3ijf7X6O 9vaiwQnXqCkYPNlaoTSaFmTiVP2TcHErDV2NQ5lfxCZnaoNIUD0ZUCcigF6k= 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:6808:16ab:b0:495:fb5e:301b with SMTP id 5614622812f47-4a4b20f444bmr3719422b6e.12.1784263143826; Thu, 16 Jul 2026 21:39:03 -0700 (PDT) Date: Thu, 16 Jul 2026 21:39:03 -0700 In-Reply-To: <20260717000803.14708-1-kartikey406@gmail.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a59b1e7.5622734e.c905.003c.GAE@google.com> Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (3) From: syzbot To: kartikey406@gmail.com, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: possible deadlock in ext4_write_inline_data_end loop0: detected capacity change from 0 to 1024 EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. ============================================ WARNING: possible recursive locking detected syzkaller #0 Not tainted -------------------------------------------- syz.0.17/5361 is trying to acquire lock: ffff0000ee0c30f8 (&ei->i_data_sem#2){++++}-{4:4}, at: ext4_update_i_disksize fs/ext4/ext4.h:3569 [inline] ffff0000ee0c30f8 (&ei->i_data_sem#2){++++}-{4:4}, at: ext4_update_inode_size fs/ext4/ext4.h:3585 [inline] ffff0000ee0c30f8 (&ei->i_data_sem#2){++++}-{4:4}, at: ext4_write_inline_data_end+0x500/0x9d8 fs/ext4/inline.c:839 but task is already holding lock: ffff0000ee0c30f8 (&ei->i_data_sem#2){++++}-{4:4}, at: ext4_write_end+0x16c/0x9fc fs/ext4/inode.c:1453 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&ei->i_data_sem#2); lock(&ei->i_data_sem#2); *** DEADLOCK *** May be due to missing lock nesting notation 4 locks held by syz.0.17/5361: #0: ffff0000d18615f0 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x100/0x144 fs/file.c:1259 #1: ffff0000db5fc450 (sb_writers#3){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2733 [inline] #1: ffff0000db5fc450 (sb_writers#3){.+.+}-{0:0}, at: vfs_write+0x248/0xa0c fs/read_write.c:683 #2: ffff0000ee0c3260 (&sb->s_type->i_mutex_key#10){++++}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline] #2: ffff0000ee0c3260 (&sb->s_type->i_mutex_key#10){++++}-{4:4}, at: ext4_buffered_write_iter+0xa0/0x2ec fs/ext4/file.c:311 #3: ffff0000ee0c30f8 (&ei->i_data_sem#2){++++}-{4:4}, at: ext4_write_end+0x16c/0x9fc fs/ext4/inode.c:1453 stack backtrace: CPU: 0 UID: 0 PID: 5361 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/02/2026 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack+0x30/0x40 lib/dump_stack.c:94 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_deadlock_bug+0x2e8/0x2f0 kernel/locking/lockdep.c:3041 check_deadlock kernel/locking/lockdep.c:3093 [inline] validate_chain kernel/locking/lockdep.c:3895 [inline] __lock_acquire+0x2764/0x2ebc kernel/locking/lockdep.c:5237 lock_acquire+0x140/0x364 kernel/locking/lockdep.c:5868 down_write+0x50/0xc0 kernel/locking/rwsem.c:1631 ext4_update_i_disksize fs/ext4/ext4.h:3569 [inline] ext4_update_inode_size fs/ext4/ext4.h:3585 [inline] ext4_write_inline_data_end+0x500/0x9d8 fs/ext4/inline.c:839 ext4_write_end+0x328/0x9fc fs/ext4/inode.c:1457 ext4_da_write_end+0x90/0xba0 fs/ext4/inode.c:3303 generic_perform_write+0x504/0x7a4 mm/filemap.c:4379 ext4_buffered_write_iter+0xd0/0x2ec fs/ext4/file.c:316 ext4_file_write_iter+0x1dc/0x134c fs/ext4/file.c:-1 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x51c/0xa0c fs/read_write.c:687 ksys_write+0x12c/0x228 fs/read_write.c:739 __do_sys_write fs/read_write.c:750 [inline] __se_sys_write fs/read_write.c:747 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:747 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140 el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:736 el0t_64_sync_handler+0x48/0x148 arch/arm64/kernel/entry-common.c:755 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594 Tested on: commit: a13c140c Linux 7.2-rc3 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=13068cb9580000 kernel config: https://syzkaller.appspot.com/x/.config?x=ecdef466b08b9772 dashboard link: https://syzkaller.appspot.com/bug?extid=293a57918b36cfae3d48 compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 userspace arch: arm64 patch: https://syzkaller.appspot.com/x/patch.diff?x=17dfcc32580000