From: syzbot <syzbot+3db654d91b471c4d7a7d@syzkaller.appspotmail.com>
To: adarshdas950@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in ntfs_evict_inode
Date: Sun, 20 Sep 2026 03:02:02 -0700 [thread overview]
Message-ID: <6aafaf1a.3179f8cd.1e36b2.000a.GAE@google.com> (raw)
In-Reply-To: <20260920092811.61884-1-adarshdas950@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in ntfs_evict_inode
------------[ cut here ]------------
ifs_is_fully_uptodate(folio, ifs) != folio_test_uptodate(folio)
WARNING: fs/iomap/buffered-io.c:295 at ifs_free+0x34a/0x410 fs/iomap/buffered-io.c:294, CPU#0: syz-executor/6336
Modules linked in:
CPU: 0 UID: 0 PID: 6336 Comm: syz-executor Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:ifs_free+0x34a/0x410 fs/iomap/buffered-io.c:294
Code: 41 5f 5d e9 b8 66 c1 ff e8 83 47 61 ff 90 0f 0b 90 e9 d5 fe ff ff e8 75 47 61 ff 90 0f 0b 90 e9 12 ff ff ff e8 67 47 61 ff 90 <0f> 0b 90 eb c7 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 08 fe ff ff
RSP: 0018:ffffc90004fbf698 EFLAGS: 00010293
RAX: ffffffff826553f9 RBX: 0000000000000008 RCX: ffff88802da69f40
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 000000008265d201 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff940003014e9 R12: ffff88803c80be84
R13: ffff88803c80be00 R14: ffffea000180a740 R15: 0000000000000000
FS: 000055555e6ba500(0000) GS:ffff888125bc8000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe150dcd000 CR3: 00000000433cc000 CR4: 00000000003526f0
Call Trace:
<TASK>
folio_invalidate mm/truncate.c:140 [inline]
truncate_cleanup_folio+0xcb/0x190 mm/truncate.c:160
truncate_inode_pages_range+0x2c4/0xd80 mm/truncate.c:404
ntfs_evict_inode+0x19/0x40 fs/ntfs3/inode.c:2012
evict+0x624/0xb50 fs/inode.c:822
dispose_list fs/inode.c:864 [inline]
evict_inodes+0x7e3/0x870 fs/inode.c:918
generic_shutdown_super+0xaa/0x2d0 fs/super.c:741
kill_block_super+0x44/0xa0 fs/super.c:1904
ntfs3_kill_sb+0x44/0x1c0 fs/ntfs3/super.c:1940
deactivate_locked_super+0xbc/0x110 fs/super.c:589
cleanup_mnt+0x3d3/0x460 fs/namespace.c:1317
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:70 [inline]
exit_to_user_mode_loop+0x204/0x770 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:343 [inline]
do_syscall_64+0x328/0x520 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f3fd9b1f397
Code: a2 c7 05 5c 43 25 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:00007ffce2e41e08 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f3fd9bb44bb RCX: 00007f3fd9b1f397
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffce2e41ec0
RBP: 00007ffce2e41ec0 R08: 00007ffce2e42ec0 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffce2e42f50
R13: 00007f3fd9bb44bb R14: 000000000003663f R15: 00007ffce2e42f90
</TASK>
Tested on:
commit: 518e5b79 Merge tag 'for-7.3-rc3-tag' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17474005580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a5341e268a22b76d
dashboard link: https://syzkaller.appspot.com/bug?extid=3db654d91b471c4d7a7d
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=16357ff9580000
next parent reply other threads:[~2026-09-20 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260920092811.61884-1-adarshdas950@gmail.com>
2026-09-20 10:02 ` syzbot [this message]
[not found] <20260920125248.93589-1-adarshdas950@gmail.com>
2026-09-20 12:54 ` syzbot
[not found] <20260920110110.75714-1-adarshdas950@gmail.com>
2026-09-20 11:14 ` syzbot
[not found] <20260920103426.72689-1-adarshdas950@gmail.com>
2026-09-20 10:55 ` syzbot
[not found] <edc7bd47-15f6-4c16-8dc0-0753712d53ed@gmail.com>
2026-09-20 9:23 ` syzbot
2026-09-17 5:53 syzbot
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=6aafaf1a.3179f8cd.1e36b2.000a.GAE@google.com \
--to=syzbot+3db654d91b471c4d7a7d@syzkaller.appspotmail.com \
--cc=adarshdas950@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®