From: syzbot <syzbot+5aea413a54e976f31725@syzkaller.appspotmail.com>
To: konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
linux-nilfs@vger.kernel.org, slava@dubeyko.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [nilfs?] WARNING in nilfs_copy_dirty_pages
Date: Sat, 05 Sep 2026 21:19:30 -0700 [thread overview]
Message-ID: <6a9ce9d2.0a3344eb.391530.0018.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 89a312991dc6 Merge tag 'cifs-fixes-7.3-rc2' of https://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11a5f349580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e909ffe6b35dddb7
dashboard link: https://syzkaller.appspot.com/bug?extid=5aea413a54e976f31725
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-89a31299.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/114a4744ab8e/vmlinux-89a31299.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c65021627f2c/bzImage-89a31299.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5aea413a54e976f31725@syzkaller.appspotmail.com
NILFS (loop0): mounting fs with errors
------------[ cut here ]------------
inconsistent dirty state
WARNING: fs/nilfs2/page.c:263 at nilfs_copy_dirty_pages+0x49f/0x6a0 fs/nilfs2/page.c:262, CPU#0: syz.0.0/5326
Modules linked in:
CPU: 0 UID: 0 PID: 5326 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:nilfs_copy_dirty_pages+0x49f/0x6a0 fs/nilfs2/page.c:262
Code: c7 ae 60 fe 4d 8b 36 44 89 f6 83 e6 01 31 ff e8 b7 4c ef fd 41 f6 c6 01 0f 85 f1 00 00 00 e8 e8 46 ef fd 48 8d 3d 01 5c aa 0c <67> 48 0f b9 3a e9 67 ff ff ff e8 d2 46 ef fd 48 c7 c7 60 7a 31 8f
RSP: 0018:ffffc9000f4274e0 EFLAGS: 00010287
RAX: ffffffff83d88548 RBX: ffffea00010e0080 RCX: 0000000000100000
RDX: ffffc9000f689000 RSI: 00000000000003d0 RDI: ffffffff9082e150
RBP: ffffc9000f4276f8 R08: ffffea00010e0087 R09: 1ffffd400021c010
R10: dffffc0000000000 R11: fffff9400021c011 R12: dffffc0000000000
R13: ffffea00010e0088 R14: 0000000062000400 R15: 0000000000000000
FS: 00007f95373936c0(0000) GS:ffff88808c2cf000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000020000000b038 CR3: 0000000040631000 CR4: 0000000000352ef0
Call Trace:
<TASK>
nilfs_mdt_save_to_shadow_map+0xbb/0x1c0 fs/nilfs2/mdt.c:552
nilfs_clean_segments+0x28d/0xbe0 fs/nilfs2/segment.c:2546
nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:938 [inline]
nilfs_ioctl+0x2619/0x2780 fs/nilfs2/ioctl.c:1368
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f953659e159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9537392fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f9536826090 RCX: 00007f953659e159
RDX: 0000200000000040 RSI: 0000000040786e88 RDI: 0000000000000006
RBP: 00007f9536635024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f9536826128 R14: 00007f9536826090 R15: 00007fff3c0fc038
</TASK>
----------------
Code disassembly (best guess), 3 bytes skipped:
0: fe 4d 8b decb -0x75(%rbp)
3: 36 44 89 f6 ss mov %r14d,%esi
7: 83 e6 01 and $0x1,%esi
a: 31 ff xor %edi,%edi
c: e8 b7 4c ef fd call 0xfdef4cc8
11: 41 f6 c6 01 test $0x1,%r14b
15: 0f 85 f1 00 00 00 jne 0x10c
1b: e8 e8 46 ef fd call 0xfdef4708
20: 48 8d 3d 01 5c aa 0c lea 0xcaa5c01(%rip),%rdi # 0xcaa5c28
* 27: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2c: e9 67 ff ff ff jmp 0xffffff98
31: e8 d2 46 ef fd call 0xfdef4708
36: 48 c7 c7 60 7a 31 8f mov $0xffffffff8f317a60,%rdi
---
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
reply other threads:[~2026-09-06 4:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a9ce9d2.0a3344eb.391530.0018.GAE@google.com \
--to=syzbot+5aea413a54e976f31725@syzkaller.appspotmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=syzkaller-bugs@googlegroups.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.