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: <670fbf7e.050a0220.d9b66.016b.GAE@google.com>
Date: Wed, 16 Oct 2024 06:28:30 -0700
From: syzbot <syzbot+d3bebcf5d53a3b1a2019@...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

Hello,

syzbot found the following issue on:

HEAD commit:    9e4c6c1ad9a1 Merge tag 'io_uring-6.12-20241011' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a07b27980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7cd9e7e4a8a0a15b
dashboard link: https://syzkaller.appspot.com/bug?extid=d3bebcf5d53a3b1a2019
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/f74026db2f8c/disk-9e4c6c1a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f9344dfaa631/vmlinux-9e4c6c1a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7282ccb66a08/bzImage-9e4c6c1a.xz

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

segctord: attempt to access beyond end of device
loop5: rw=0, sector=464, nr_sectors = 8 limit=0
NILFS (loop5): I/O error reading meta-data file (ino=3, block-offset=2)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9015 at fs/nilfs2/segment.c:1500 nilfs_cancel_segusage fs/nilfs2/segment.c:1500 [inline]
WARNING: CPU: 0 PID: 9015 at fs/nilfs2/segment.c:1500 nilfs_segctor_abort_construction+0xe51/0xec0 fs/nilfs2/segment.c:1866
Modules linked in:
CPU: 0 UID: 0 PID: 9015 Comm: segctord Not tainted 6.12.0-rc2-syzkaller-00260-g9e4c6c1ad9a1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:nilfs_cancel_segusage fs/nilfs2/segment.c:1500 [inline]
RIP: 0010:nilfs_segctor_abort_construction+0xe51/0xec0 fs/nilfs2/segment.c:1866
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 c0 6c 75 08 e8 00 13 1a fe 90 <0f> 0b 90 e9 ea f9 ff ff e8 f2 12 1a fe 90 0f 0b 90 e9 93 fb ff ff
RSP: 0018:ffffc9000326f680 EFLAGS: 00010293
RAX: ffffffff837ad450 RBX: 00000000fffffffb RCX: ffff888026890000
RDX: 0000000000000000 RSI: 00000000fffffffb RDI: 0000000000000000
RBP: ffffc9000326f770 R08: ffffffff837ace36 R09: 1ffff1100d2d1b40
R10: dffffc0000000000 R11: ffffed100d2d1b41 R12: 000000000000000e
R13: 0000000000000003 R14: ffff88805b1f26e8 R15: ffff888070060e18
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000559d87803680 CR3: 000000002d42e000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 nilfs_segctor_do_construct+0x6335/0x6b90 fs/nilfs2/segment.c:2179
 nilfs_segctor_construct+0x181/0x6b0 fs/nilfs2/segment.c:2479
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline]
 nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701
 kthread+0x2f2/0x390 kernel/kthread.c:389
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147
 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