[moderation] [reiserfs?] BUG: corrupted list in reiserfs_ioctl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 92901222f83d Merge tag 'f2fs-for-6-6-rc1' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d75d98680000
kernel config: https://syzkaller.appspot.com/x/.config?x=3d78b3780d210e21
dashboard link: https://syzkaller.appspot.com/bug?extid=36000e842074d963412e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org reiserf...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f58f2fdc5a9e/disk-92901222.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/16dba3905664/vmlinux-92901222.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3a5b1d5efdbd/bzImage-92901222.xz

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

loop3: detected capacity change from 0 to 8
list_add corruption. prev is NULL.
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:26!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4248 Comm: syz-executor.3 Not tainted 6.5.0-syzkaller-11075-g92901222f83d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:__list_add_valid_or_report+0xac/0xf0 lib/list_debug.c:25
Code: 41 5d 41 5e 41 5f c3 48 c7 c7 60 77 59 8b 4c 89 fe 4c 89 e2 4c 89 f1 e8 72 17 83 06 0f 0b 48 c7 c7 60 75 59 8b e8 64 17 83 06 <0f> 0b 48 c7 c7 00 76 59 8b e8 56 17 83 06 0f 0b 48 c7 c7 60 76 59
RSP: 0018:ffffc90003457cd0 EFLAGS: 00010246
RAX: 0000000000000022 RBX: 1ffff11004fc0490 RCX: 6997bca836d24f00
RDX: ffffc9000bcda000 RSI: 0000000000002286 RDI: 0000000000002287
RBP: ffffc90003457e68 R08: ffffffff8170a5ec R09: 1ffff9200068af4c
R10: dffffc0000000000 R11: fffff5200068af4d R12: 0000000000000000
R13: dffffc0000000000 R14: ffff888027e02480 R15: ffff888027e02478
FS: 00007f0bdd67f6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0bdc90642e CR3: 0000000019f11000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_add_valid include/linux/list.h:88 [inline]
__list_add include/linux/list.h:150 [inline]
list_add_tail include/linux/list.h:183 [inline]
__mutex_add_waiter kernel/locking/mutex.c:210 [inline]
__mutex_lock_common+0x75f/0x2530 kernel/locking/mutex.c:637
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27
reiserfs_ioctl+0x74/0x2f0 fs/reiserfs/ioctl.c:81
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0bdc87cae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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:00007f0bdd67f0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f0bdc99bf80 RCX: 00007f0bdc87cae9
RDX: 0000000020000040 RSI: 00000000c0189372 RDI: 0000000000000005
RBP: 00007f0bdc8c847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f0bdc99bf80 R15: 00007ffe089319b8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_add_valid_or_report+0xac/0xf0 lib/list_debug.c:25
Code: 41 5d 41 5e 41 5f c3 48 c7 c7 60 77 59 8b 4c 89 fe 4c 89 e2 4c 89 f1 e8 72 17 83 06 0f 0b 48 c7 c7 60 75 59 8b e8 64 17 83 06 <0f> 0b 48 c7 c7 00 76 59 8b e8 56 17 83 06 0f 0b 48 c7 c7 60 76 59
RSP: 0018:ffffc90003457cd0 EFLAGS: 00010246
RAX: 0000000000000022 RBX: 1ffff11004fc0490 RCX: 6997bca836d24f00
RDX: ffffc9000bcda000 RSI: 0000000000002286 RDI: 0000000000002287
RBP: ffffc90003457e68 R08: ffffffff8170a5ec R09: 1ffff9200068af4c
R10: dffffc0000000000 R11: fffff5200068af4d R12: 0000000000000000
R13: dffffc0000000000 R14: ffff888027e02480 R15: ffff888027e02478
FS: 00007f0bdd67f6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0bdc90642e CR3: 0000000019f11000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.