linux-kernel - [syzbot] [nilfs?] WARNING in nilfs_segctor_abort

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <67a5b618.050a0220.2b1e6.0018.GAE@google.com>
Date: Thu, 06 Feb 2025 23:28:24 -0800
From: syzbot <syzbot+86e5da039cef3ad11c6e@...kaller.appspotmail.com>
To: konishi.ryusuke@...il.com, linux-kernel@...r.kernel.org, 
	linux-nilfs@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [nilfs?] WARNING in nilfs_segctor_abort_construction (2)

Hello,

syzbot found the following issue on:

HEAD commit:    69e858e0b8b2 Merge tag 'uml-for-linus-6.14-rc1' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=127db5f8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d033b14aeef39158
dashboard link: https://syzkaller.appspot.com/bug?extid=86e5da039cef3ad11c6e
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0c358838d66a/disk-69e858e0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/29a6852a21ee/vmlinux-69e858e0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fb214c6e7c43/bzImage-69e858e0.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+86e5da039cef3ad11c6e@...kaller.appspotmail.com

segctord: attempt to access beyond end of device
loop4: rw=0, sector=80, nr_sectors = 2 limit=0
NILFS (loop4): I/O error reading meta-data file (ino=5, block-offset=0)
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6772 at fs/nilfs2/segment.c:1507 nilfs_cancel_segusage fs/nilfs2/segment.c:1507 [inline]
WARNING: CPU: 1 PID: 6772 at fs/nilfs2/segment.c:1507 nilfs_segctor_abort_construction+0xe51/0xec0 fs/nilfs2/segment.c:1873
Modules linked in:
CPU: 1 UID: 0 PID: 6772 Comm: segctord Not tainted 6.13.0-syzkaller-09760-g69e858e0b8b2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:nilfs_cancel_segusage fs/nilfs2/segment.c:1507 [inline]
RIP: 0010:nilfs_segctor_abort_construction+0xe51/0xec0 fs/nilfs2/segment.c:1873
Code: 8b 04 25 28 00 00 00 48 3b 84 24 a0 00 00 00 75 74 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d e9 d0 38 6d fd e8 80 64 1c fe 90 <0f> 0b 90 e9 ea f9 ff ff e8 72 64 1c fe 90 0f 0b 90 e9 93 fb ff ff
RSP: 0018:ffffc90003adf5e0 EFLAGS: 00010293
RAX: ffffffff83a30840 RBX: 00000000fffffffb RCX: ffff888025700000
RDX: 0000000000000000 RSI: 00000000fffffffb RDI: 0000000000000000
RBP: ffffc90003adf6d0 R08: ffffffff83a30226 R09: 1ffff1100457f180
R10: dffffc0000000000 R11: ffffed100457f181 R12: 000000000000002f
R13: 0000000000000000 R14: ffff888057ef0008 R15: ffff888055c9a138
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f579116b440 CR3: 000000000e738000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 nilfs_segctor_do_construct+0x6615/0x6ea0 fs/nilfs2/segment.c:2186
 nilfs_segctor_construct+0x181/0x6b0 fs/nilfs2/segment.c:2478
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2586 [inline]
 nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2700
 kthread+0x7ab/0x920 kernel/kthread.c:464
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>


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