All of lore.kernel.org
 help / color / mirror / Atom feed
From: "yebin (H)" <yebin10@huawei.com>
To: syzbot ci <syzbot+cif302214182590c61@syzkaller.appspotmail.com>,
	<adilger.kernel@dilger.ca>, <jack@suse.cz>,
	<linux-ext4@vger.kernel.org>, <tytso@mit.edu>,
	<yebin@huaweicloud.com>
Cc: <syzbot@lists.linux.dev>, <syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot ci] Re: ext4: test if inode's all dirty pages are submitted to disk
Date: Sat, 28 Feb 2026 09:14:28 +0800	[thread overview]
Message-ID: <69A24174.2080805@huawei.com> (raw)
In-Reply-To: <69a14d31.050a0220.305b49.00aa.GAE@google.com>

This is my oversight. If the file system has already become read-only
and dirty pages cannot be flushed back, no warning should be generated
at this time.

On 2026/2/27 15:52, syzbot ci wrote:
> syzbot ci has tested the following series
>
> [v1] ext4: test if inode's all dirty pages are submitted to disk
> https://lore.kernel.org/all/20260226110718.1904825-1-yebin@huaweicloud.com
> * [PATCH] ext4: test if inode's all dirty pages are submitted to disk
>
> and found the following issue:
> WARNING in ext4_evict_inode
>
> Full report is available here:
> https://ci.syzbot.org/series/8f9434e5-a73c-4b31-be9f-e9b76f1c2596
>
> ***
>
> WARNING in ext4_evict_inode
>
> tree:      torvalds
> URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
> base:      f4d0ec0aa20d49f09dc01d82894ce80d72de0560
> arch:      amd64
> compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> config:    https://ci.syzbot.org/builds/7053c6f2-2ee6-4a1d-9f74-d2f56facd9f9/config
> C repro:   https://ci.syzbot.org/findings/4f7c2b91-8121-443d-9a4f-991feda8057c/c_repro
> syz repro: https://ci.syzbot.org/findings/4f7c2b91-8121-443d-9a4f-991feda8057c/syz_repro
>
> ------------[ cut here ]------------
> mapping_tagged(&inode->i_data, PAGECACHE_TAG_DIRTY)
> WARNING: fs/ext4/inode.c:191 at ext4_evict_inode+0xbdc/0xf10 fs/ext4/inode.c:191, CPU#1: syz-executor/5915
> Modules linked in:
> CPU: 1 UID: 0 PID: 5915 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:ext4_evict_inode+0xbdc/0xf10 fs/ext4/inode.c:191
> Code: ba 2c 02 00 48 8b bc 24 a0 00 00 00 e8 bd 49 14 00 e9 71 fe ff ff e8 43 63 40 ff 90 0f 0b 90 e9 e6 f4 ff ff e8 35 63 40 ff 90 <0f> 0b 90 e9 f2 f5 ff ff e8 27 63 40 ff 48 8d 3d 50 df 92 0d 67 48
> RSP: 0018:ffffc900048b79a0 EFLAGS: 00010293
> RAX: ffffffff8285287b RBX: ffff88811d980298 RCX: ffff8881027d8000
> RDX: 0000000000000000 RSI: 0000000004000000 RDI: 0000000000000000
> RBP: ffffc900048b7ab0 R08: ffffffff901181b7 R09: 1ffffffff2023036
> R10: dffffc0000000000 R11: fffffbfff2023037 R12: 1ffff92000916f44
> R13: dffffc0000000000 R14: ffff88811d9804b8 R15: 0000000004000000
> FS:  000055557d541500(0000) GS:ffff8882a9464000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000000c00003e720 CR3: 000000010f9d2000 CR4: 00000000000006f0
> Call Trace:
>   <TASK>
>   evict+0x61e/0xb10 fs/inode.c:846
>   dispose_list fs/inode.c:888 [inline]
>   evict_inodes+0x75a/0x7f0 fs/inode.c:942
>   generic_shutdown_super+0xaa/0x2d0 fs/super.c:632
>   kill_block_super+0x44/0x90 fs/super.c:1725
>   ext4_kill_sb+0x68/0xb0 fs/ext4/super.c:7459
>   deactivate_locked_super+0xbc/0x130 fs/super.c:476
>   cleanup_mnt+0x437/0x4d0 fs/namespace.c:1312
>   task_work_run+0x1d9/0x270 kernel/task_work.c:233
>   resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
>   __exit_to_user_mode_loop kernel/entry/common.c:67 [inline]
>   exit_to_user_mode_loop+0xed/0x480 kernel/entry/common.c:98
>   __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
>   syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
>   syscall_exit_to_user_mode include/linux/entry-common.h:325 [inline]
>   do_syscall_64+0x32d/0xf80 arch/x86/entry/syscall_64.c:100
>   entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7fcf3c79d897
> Code: a2 c7 05 5c ee 24 00 00 00 00 00 eb 96 e8 e1 12 00 00 90 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8
> RSP: 002b:00007ffe2362cef8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
> RAX: 0000000000000000 RBX: 00007fcf3c831ef0 RCX: 00007fcf3c79d897
> RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe2362cfb0
> RBP: 00007ffe2362cfb0 R08: 00007ffe2362dfb0 R09: 00000000ffffffff
> R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe2362e040
> R13: 00007fcf3c831ef0 R14: 000000000000f11c R15: 00007ffe2362e080
>   </TASK>
>
>
> ***
>
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
>    Tested-by: syzbot@syzkaller.appspotmail.com
>
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at syzkaller@googlegroups.com.
>
>
> .
>

  reply	other threads:[~2026-02-28  1:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 11:07 [PATCH] ext4: test if inode's all dirty pages are submitted to disk Ye Bin
2026-02-26 13:44 ` Jan Kara
2026-02-27  7:52 ` [syzbot ci] " syzbot ci
2026-02-28  1:14   ` yebin (H) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-28  2:56 [PATCH v2] " Ye Bin
2026-03-02 10:08 ` [syzbot ci] " syzbot ci
2026-03-02 14:08   ` yebin (H)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=69A24174.2080805@huawei.com \
    --to=yebin10@huawei.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=syzbot+cif302214182590c61@syzkaller.appspotmail.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    --cc=yebin@huaweicloud.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.