public inbox for ntfs3@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot <syzbot+57f9327d593d301ce2a2@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
	linux-kernel@vger.kernel.org,  ntfs3@lists.linux.dev,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in errseq_set (2)
Date: Wed, 07 May 2025 20:20:29 -0700	[thread overview]
Message-ID: <681c22fd.050a0220.a19a9.009d.GAE@google.com> (raw)
In-Reply-To: <67810cc6.050a0220.216c54.000a.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    707df3375124 Merge tag 'media/v6.15-2' of git://git.kernel..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=173c8670580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b9683d529ec1b880
dashboard link: https://syzkaller.appspot.com/bug?extid=57f9327d593d301ce2a2
compiler:       Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11ae0768580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17fa98f4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b678b69ad07a/disk-707df337.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/747856a66c71/vmlinux-707df337.xz
kernel image: https://storage.googleapis.com/syzbot-assets/69a1d9539047/bzImage-707df337.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/44a5023af4cf/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+57f9327d593d301ce2a2@syzkaller.appspotmail.com

------------[ cut here ]------------
err = 556
WARNING: CPU: 1 PID: 5826 at lib/errseq.c:75 errseq_set+0xed/0x120 lib/errseq.c:74
Modules linked in:
CPU: 1 UID: 0 PID: 5826 Comm: syz-executor335 Not tainted 6.15.0-rc5-syzkaller-00038-g707df3375124 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/29/2025
RIP: 0010:errseq_set+0xed/0x120 lib/errseq.c:74
Code: 5b 41 5c 41 5e 41 5f 5d c3 cc cc cc cc cc e8 3a 4a 0e fd eb e9 e8 33 4a 0e fd 90 48 c7 c7 80 b5 c0 8b 89 de e8 84 a6 d2 fc 90 <0f> 0b 90 90 eb ce 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 2f ff ff
RSP: 0018:ffffc900041c73a0 EFLAGS: 00010246
RAX: 5edf3f3cab771a00 RBX: 000000000000022c RCX: ffff888033313c00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 0000000000000000 R08: ffff8880b8923e93 R09: 1ffff110171247d2
R10: dffffc0000000000 R11: ffffed10171247d3 R12: ffff8880769766d0
R13: dffffc0000000000 R14: ffff888076976c70 R15: ffff888076976768
FS:  00007fd18cfee6c0(0000) GS:ffff8881261fd000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd184bffe00 CR3: 0000000077516000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __filemap_set_wb_err+0x22/0x1e0 mm/filemap.c:711
 mapping_set_error include/linux/pagemap.h:244 [inline]
 ntfs_resident_writepage+0x114/0x200 fs/ntfs3/inode.c:886
 write_cache_pages+0x61/0x100 mm/page-writeback.c:2613
 do_writepages+0x3ae/0x7b0 mm/page-writeback.c:2656
 filemap_fdatawrite_wbc mm/filemap.c:386 [inline]
 __filemap_fdatawrite_range mm/filemap.c:419 [inline]
 filemap_write_and_wait_range+0x217/0x310 mm/filemap.c:691
 kiocb_write_and_wait mm/filemap.c:2792 [inline]
 generic_file_read_iter+0x19f/0x510 mm/filemap.c:2866
 copy_splice_read+0x54f/0x9b0 fs/splice.c:363
 do_splice_read fs/splice.c:978 [inline]
 splice_direct_to_actor+0x4d0/0xcc0 fs/splice.c:1083
 do_splice_direct_actor fs/splice.c:1201 [inline]
 do_splice_direct+0x181/0x270 fs/splice.c:1227
 do_sendfile+0x4da/0x7d0 fs/read_write.c:1368
 __do_sys_sendfile64 fs/read_write.c:1429 [inline]
 __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1415
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd18d039e89
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 18 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd18cfee218 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fd18d0e16c8 RCX: 00007fd18d039e89
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000004
RBP: 00007fd18d0e16c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000fffe80 R11: 0000000000000246 R12: 00007fd18d0ad820
R13: 0000200000000100 R14: 0000200000000400 R15: 0000200000000080
 </TASK>


---
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.

      reply	other threads:[~2025-05-08  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 12:04 [syzbot] [ntfs3?] WARNING in errseq_set (2) syzbot
2025-05-08  3:20 ` syzbot [this message]

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=681c22fd.050a0220.a19a9.009d.GAE@google.com \
    --to=syzbot+57f9327d593d301ce2a2@syzkaller.appspotmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --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