From: syzbot <syzbot+f5d91b1897d5b094c6b4@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, chao@kernel.org,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab@kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] WARNING in get_data
Date: Sun, 09 Nov 2025 02:15:33 -0800 [thread overview]
Message-ID: <691069c5.a70a0220.22f260.00aa.GAE@google.com> (raw)
In-Reply-To: <68fc0765.a00a0220.9662e.000e.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 9c0826a5d9aa Add linux-next specific files for 20251107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11c44b42580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f2ebeee52bf052b8
dashboard link: https://syzkaller.appspot.com/bug?extid=f5d91b1897d5b094c6b4
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16263084580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14496a92580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/32b5c04a0baa/disk-9c0826a5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9438206c142a/vmlinux-9c0826a5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/129cd0208baa/bzImage-9c0826a5.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/be89fc48acf0/mount_3.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f5d91b1897d5b094c6b4@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 4096
ntfs3(loop0): Different NTFS sector size (1024) and media sector size (512).
------------[ cut here ]------------
WARNING: kernel/printk/printk_ringbuffer.c:1278 at get_data+0x48a/0x840 kernel/printk/printk_ringbuffer.c:1278, CPU#1: syz.0.541/6553
Modules linked in:
CPU: 1 UID: 0 PID: 6553 Comm: syz.0.541 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:get_data+0x48a/0x840 kernel/printk/printk_ringbuffer.c:1278
Code: 83 c4 f8 48 b8 00 00 00 00 00 fc ff df 41 0f b6 04 07 84 c0 0f 85 ee 01 00 00 44 89 65 00 49 83 c5 08 eb 13 e8 87 47 1f 00 90 <0f> 0b 90 eb 05 e8 7c 47 1f 00 45 31 ed 4c 89 e8 48 83 c4 28 5b 41
RSP: 0018:ffffc9000c0eec40 EFLAGS: 00010293
RAX: ffffffff81a238a9 RBX: 00003fffffffffff RCX: ffff888026123d00
RDX: 0000000000000000 RSI: 00003fffffffffff RDI: 0000000000000000
RBP: 0000000000000012 R08: 0000000000000f4d R09: 0000003b6994bf6b
R10: 0000003b6994bf6b R11: 0000199962000021 R12: 0000000000000012
R13: 0000000000000000 R14: ffffc9000c0eed88 R15: 1ffffffff1bca6c2
FS: 000055557ac66500(0000) GS:ffff888125fc2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffec7fad000 CR3: 000000002ea20000 CR4: 00000000003526f0
Call Trace:
<TASK>
copy_data kernel/printk/printk_ringbuffer.c:1857 [inline]
prb_read kernel/printk/printk_ringbuffer.c:1966 [inline]
_prb_read_valid+0x672/0xa90 kernel/printk/printk_ringbuffer.c:2143
prb_read_valid+0x3c/0x60 kernel/printk/printk_ringbuffer.c:2215
printk_get_next_message+0x15c/0x7b0 kernel/printk/printk.c:2978
console_emit_next_record kernel/printk/printk.c:3062 [inline]
console_flush_one_record kernel/printk/printk.c:3194 [inline]
console_flush_all+0x4cc/0xb10 kernel/printk/printk.c:3268
__console_flush_and_unlock kernel/printk/printk.c:3298 [inline]
console_unlock+0xbb/0x190 kernel/printk/printk.c:3338
vprintk_emit+0x4c5/0x590 kernel/printk/printk.c:2423
_printk+0xcf/0x120 kernel/printk/printk.c:2448
ntfs_inode_printk+0x5fd/0x700 fs/ntfs3/super.c:156
ntfs_bad_inode+0x71/0x150 fs/ntfs3/fsntfs.c:910
mi_enum_attr+0x7b9/0x9f0 fs/ntfs3/record.c:352
ntfs_read_mft fs/ntfs3/inode.c:123 [inline]
ntfs_iget5+0x245b/0x3860 fs/ntfs3/inode.c:542
ntfs_fill_super+0x23ce/0x43d0 fs/ntfs3/super.c:1284
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1692
vfs_get_tree+0x92/0x2b0 fs/super.c:1752
fc_mount fs/namespace.c:1198 [inline]
do_new_mount_fc fs/namespace.c:3641 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3717
do_mount fs/namespace.c:4040 [inline]
__do_sys_mount fs/namespace.c:4228 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4205
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f6530f90e6a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffec7fac3c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffec7fac450 RCX: 00007f6530f90e6a
RDX: 00002000000002c0 RSI: 0000200000000040 RDI: 00007ffec7fac410
RBP: 00002000000002c0 R08: 00007ffec7fac450 R09: 0000000000000082
R10: 0000000000000082 R11: 0000000000000246 R12: 0000200000000040
R13: 00007ffec7fac410 R14: 000000000001f853 R15: 00002000000000c0
</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.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+f5d91b1897d5b094c6b4@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, chao@kernel.org,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab@kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] WARNING in get_data
Date: Sun, 09 Nov 2025 02:15:33 -0800 [thread overview]
Message-ID: <691069c5.a70a0220.22f260.00aa.GAE@google.com> (raw)
In-Reply-To: <68fc0765.a00a0220.9662e.000e.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 9c0826a5d9aa Add linux-next specific files for 20251107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11c44b42580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f2ebeee52bf052b8
dashboard link: https://syzkaller.appspot.com/bug?extid=f5d91b1897d5b094c6b4
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16263084580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14496a92580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/32b5c04a0baa/disk-9c0826a5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9438206c142a/vmlinux-9c0826a5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/129cd0208baa/bzImage-9c0826a5.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/be89fc48acf0/mount_3.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f5d91b1897d5b094c6b4@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 4096
ntfs3(loop0): Different NTFS sector size (1024) and media sector size (512).
------------[ cut here ]------------
WARNING: kernel/printk/printk_ringbuffer.c:1278 at get_data+0x48a/0x840 kernel/printk/printk_ringbuffer.c:1278, CPU#1: syz.0.541/6553
Modules linked in:
CPU: 1 UID: 0 PID: 6553 Comm: syz.0.541 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:get_data+0x48a/0x840 kernel/printk/printk_ringbuffer.c:1278
Code: 83 c4 f8 48 b8 00 00 00 00 00 fc ff df 41 0f b6 04 07 84 c0 0f 85 ee 01 00 00 44 89 65 00 49 83 c5 08 eb 13 e8 87 47 1f 00 90 <0f> 0b 90 eb 05 e8 7c 47 1f 00 45 31 ed 4c 89 e8 48 83 c4 28 5b 41
RSP: 0018:ffffc9000c0eec40 EFLAGS: 00010293
RAX: ffffffff81a238a9 RBX: 00003fffffffffff RCX: ffff888026123d00
RDX: 0000000000000000 RSI: 00003fffffffffff RDI: 0000000000000000
RBP: 0000000000000012 R08: 0000000000000f4d R09: 0000003b6994bf6b
R10: 0000003b6994bf6b R11: 0000199962000021 R12: 0000000000000012
R13: 0000000000000000 R14: ffffc9000c0eed88 R15: 1ffffffff1bca6c2
FS: 000055557ac66500(0000) GS:ffff888125fc2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffec7fad000 CR3: 000000002ea20000 CR4: 00000000003526f0
Call Trace:
<TASK>
copy_data kernel/printk/printk_ringbuffer.c:1857 [inline]
prb_read kernel/printk/printk_ringbuffer.c:1966 [inline]
_prb_read_valid+0x672/0xa90 kernel/printk/printk_ringbuffer.c:2143
prb_read_valid+0x3c/0x60 kernel/printk/printk_ringbuffer.c:2215
printk_get_next_message+0x15c/0x7b0 kernel/printk/printk.c:2978
console_emit_next_record kernel/printk/printk.c:3062 [inline]
console_flush_one_record kernel/printk/printk.c:3194 [inline]
console_flush_all+0x4cc/0xb10 kernel/printk/printk.c:3268
__console_flush_and_unlock kernel/printk/printk.c:3298 [inline]
console_unlock+0xbb/0x190 kernel/printk/printk.c:3338
vprintk_emit+0x4c5/0x590 kernel/printk/printk.c:2423
_printk+0xcf/0x120 kernel/printk/printk.c:2448
ntfs_inode_printk+0x5fd/0x700 fs/ntfs3/super.c:156
ntfs_bad_inode+0x71/0x150 fs/ntfs3/fsntfs.c:910
mi_enum_attr+0x7b9/0x9f0 fs/ntfs3/record.c:352
ntfs_read_mft fs/ntfs3/inode.c:123 [inline]
ntfs_iget5+0x245b/0x3860 fs/ntfs3/inode.c:542
ntfs_fill_super+0x23ce/0x43d0 fs/ntfs3/super.c:1284
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1692
vfs_get_tree+0x92/0x2b0 fs/super.c:1752
fc_mount fs/namespace.c:1198 [inline]
do_new_mount_fc fs/namespace.c:3641 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3717
do_mount fs/namespace.c:4040 [inline]
__do_sys_mount fs/namespace.c:4228 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4205
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f6530f90e6a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffec7fac3c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffec7fac450 RCX: 00007f6530f90e6a
RDX: 00002000000002c0 RSI: 0000200000000040 RDI: 00007ffec7fac410
RBP: 00002000000002c0 R08: 00007ffec7fac450 R09: 0000000000000082
R10: 0000000000000082 R11: 0000000000000246 R12: 0000200000000040
R13: 00007ffec7fac410 R14: 000000000001f853 R15: 00002000000000c0
</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.
next prev parent reply other threads:[~2025-11-09 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 23:10 [f2fs-dev] [syzbot] [f2fs?] WARNING in get_data syzbot
2025-10-24 23:10 ` syzbot
2025-11-09 10:15 ` syzbot [this message]
2025-11-09 10:15 ` 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=691069c5.a70a0220.22f260.00aa.GAE@google.com \
--to=syzbot+f5d91b1897d5b094c6b4@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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 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.