[reiserfs?] WARNING in journal_end

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=154be1f8480000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=0e11c3467ee1b6237e8f
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17bffc54480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16410f08480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/de985f9431f4/mount_0.gz

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

REISERFS warning (device loop0): jdm-13090 reiserfs_new_inode: ACLs aren't enabled in the fs, but vfs thinks they are!
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
REISERFS error (device loop0): vs-4080 _reiserfs_free_block: block 531: bit already cleared
REISERFS (device loop0): Remounting filesystem read-only
------------[ cut here ]------------
WARNING: CPU: 1 PID: 8097 at fs/reiserfs/journal.c:3405 journal_end.cold+0x11/0x1e fs/reiserfs/journal.c:3405
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 8097 Comm: syz-executor121 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:journal_end.cold+0x11/0x1e fs/reiserfs/journal.c:3405
Code: f0 fd ff e8 50 bf 6c f9 e8 9b 82 a2 f9 48 c7 c7 00 6f 79 88 e8 bb 98 20 00 e8 3a bf 6c f9 48 c7 c7 a0 bc 79 88 e8 99 f0 fd ff <0f> 0b 41 bd fb ff ff ff e9 c2 6f e1 f9 e8 1c bf 6c f9 48 c7 c7 e0
RSP: 0018:ffff8880b1537aa8 EFLAGS: 00010286
RAX: 0000000000000024 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10162a6f47
RBP: ffff8880b1537b20 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880b1537b34
R13: 0000000000000000 R14: ffff88808ac377a8 R15: ffff8880b1537b20
reiserfs_truncate_file+0x1bc/0x1030 fs/reiserfs/inode.c:2321
reiserfs_file_release+0x982/0xd90 fs/reiserfs/file.c:115
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xbf3/0x2be0 kernel/exit.c:870
do_group_exit+0x125/0x310 kernel/exit.c:967
__do_sys_exit_group kernel/exit.c:978 [inline]
__se_sys_exit_group kernel/exit.c:976 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:976
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f3e958c2419
Code: Bad RIP value.
RSP: 002b:00007ffd28351398 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f3e95938330 RCX: 00007f3e958c2419
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f3e95938330
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c4215ee4771b Linux 4.14.302
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d43b54480000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a9988fe055c9527
dashboard link: https://syzkaller.appspot.com/bug?extid=81e9c755ef1260599dd8

compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e95ea8480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1136acbc480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c93ba055d204/disk-c4215ee4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfbc929a33c1/vmlinux-c4215ee4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/444658051770/bzImage-c4215ee4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/05f4c270ec70/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+81e9c7...@syzkaller.appspotmail.com

REISERFS warning (device loop0): jdm-13090 reiserfs_new_inode: ACLs aren't enabled in the fs, but vfs thinks they are!
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
REISERFS error (device loop0): vs-4080 _reiserfs_free_block: block 531: bit already cleared
REISERFS (device loop0): Remounting filesystem read-only
------------[ cut here ]------------

WARNING: CPU: 0 PID: 7991 at fs/reiserfs/journal.c:3402 journal_end+0x2a5/0x300 fs/reiserfs/journal.c:3402

Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 7991 Comm: syz-executor763 Not tainted 4.14.302-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:

__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:journal_end+0x2a5/0x300 fs/reiserfs/journal.c:3402
RSP: 0018:ffff88809729fb00 EFLAGS: 00010297
RAX: ffff888096142080 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880982f4ac0 RDI: ffff88809729fb80
RBP: ffff88809729fb78 R08: 0000000000000001 R09: ffff88809729fb78
R10: ffff88809729fbaf R11: ffff888096142080 R12: ffff88809729fb8c
R13: 0000000000000000 R14: ffff88808e3407b0 R15: ffff88809729fb78
reiserfs_truncate_file+0x189/0xdb0 fs/reiserfs/inode.c:2320
reiserfs_file_release+0x758/0xaf0 fs/reiserfs/file.c:115
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa44/0x2850 kernel/exit.c:868
do_group_exit+0x100/0x2e0 kernel/exit.c:965
SYSC_exit_group kernel/exit.c:976 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:974
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7fe7b42b5419
RSP: 002b:00007ffdc2457cd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007fe7b432b330 RCX: 00007fe7b42b5419

RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 00007fe7b432b330