kernel BUG at fs/reiserfs/journal.c:LINE!

[syzbot]

Hello,

syzbot hit the following crash on upstream commit
9dd2326890d89a5179967c947dab2bab34d7ddee (Fri Mar 30 17:29:47 2018 +0000)
Merge tag 'ceph-for-4.16-rc8' of git://github.com/ceph/ceph-client
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=6820505ae5978f4f8f2f

syzkaller reproducer:
https://syzkaller.appspot.com/x/repro.syz?id=5883680186695680
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=6706763961204736
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-2760467897697295172
compiler: gcc (GCC) 7.1.1 20170620

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+682050...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

REISERFS (device loop7): using 3.5.x disk format
REISERFS (device loop0): found reiserfs format "3.5" with non-standard
journal
REISERFS (device loop5): using 3.5.x disk format
REISERFS (device loop3): checking transaction log (loop3)
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:3640!
REISERFS (device loop0): using ordered data mode
invalid opcode: 0000 [#1] SMP KASAN
reiserfs: using flush barriers
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 4674 Comm: syz-executor5 Not tainted 4.16.0-rc7+ #7
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:check_journal_end fs/reiserfs/journal.c:3640 [inline]
RIP: 0010:do_journal_end+0x39ae/0x4ce0 fs/reiserfs/journal.c:4037
RSP: 0018:ffff8801aafbf1a0 EFLAGS: 00010293
RAX: ffff8801aaf0c100 RBX: ffffc9000273d000 RCX: ffffffff81e6637e
REISERFS (device loop1): found reiserfs format "3.5" with non-standard
journal
RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff8801aafbfa04
RBP: ffff8801aafbf758 R08: ffffffff81e76040 R09: 0000000000000004
R10: ffff8801aafbf168 R11: 0000000000000004 R12: 0000000000000000
R13: ffffc9000273d058 R14: ffffc9000273d048 R15: ffff8801aafbfa10
FS: 00007f3bb0f9f700(0000) GS:ffff8801db000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000625208 CR3: 00000001a9148006 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
init_special_inode: bogus i_mode (0) for inode loop4:2
REISERFS warning (device loop4): vs-13075 reiserfs_read_locked_inode: dead
inode read from disk [1 2 0x0 SD]. This is likely to be race with knfsd.
Ignore
journal_end+0x239/0x2d0 fs/reiserfs/journal.c:3409
REISERFS (device loop0): journal params: device loop0, size 512, journal
first block 18, max trans len 256, max batch 225, max commit age 30, max
trans age 30
reiserfs_fill_super+0x2a66/0x33a0 fs/reiserfs/super.c:2168
init_special_inode: bogus i_mode (0) for inode loop3:2
mount_bdev+0x2b7/0x370 fs/super.c:1119
REISERFS warning (device loop3): vs-13075 reiserfs_read_locked_inode: dead
inode read from disk [1 2 0x0 SD]. This is likely to be race with knfsd.
Ignore
get_super_block+0x34/0x40 fs/reiserfs/super.c:2605
mount_fs+0x66/0x2d0 fs/super.c:1222
vfs_kern_mount.part.26+0xc6/0x4a0 fs/namespace.c:1037
REISERFS (device loop1): using ordered data mode
vfs_kern_mount fs/namespace.c:2509 [inline]
do_new_mount fs/namespace.c:2512 [inline]
do_mount+0xea4/0x2bb0 fs/namespace.c:2842
reiserfs: using flush barriers
SYSC_mount fs/namespace.c:3058 [inline]
SyS_mount+0xab/0x120 fs/namespace.c:3035
do_syscall_64+0x281/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x4578aa
RSP: 002b:00007f3bb0f9ebb8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000000 RCX: 00000000004578aa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f3bb0f9ec00
RBP: 0000000000000007 R08: 0000000020011500 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005
R13: 000000000000066d R14: 00000000006fbad8 R15: 0000000000000001
Code: e8 c8 fe fe ff e9 b9 f9 ff ff e8 de 01 8b ff 0f 0b e8 d7 01 8b ff 0f
0b e8 d0 01 8b ff 0f 0b e8 c9 01 8b ff 0f 0b e8 c2 01 8b ff <0f> 0b 4c 8d
a5 98 fc ff ff e8 b4 01 8b ff 48 8d bb d0 01 00 00
RIP: check_journal_end fs/reiserfs/journal.c:3640 [inline] RSP:
ffff8801aafbf1a0
RIP: do_journal_end+0x39ae/0x4ce0 fs/reiserfs/journal.c:4037 RSP:
ffff8801aafbf1a0
---[ end trace 85601a98bc340fd3 ]---


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
If you want to test a patch for this bug, please reply with:
#syz test: git://repo/address.git branch
and provide the patch inline or as an attachment.
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: eb5f95f1 Merge tag 's390-5.9-6' of git://git.kernel.org/pu..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=127b7809900000
kernel config: https://syzkaller.appspot.com/x/.config?x=ffe85b197a57c180
dashboard link: https://syzkaller.appspot.com/bug?extid=6820505ae5978f4f8f2f
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a825d9900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a5c8d3900000

Bisection is inconclusive: the issue happens on the oldest tested release.

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1426e997200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1226e997200000

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

REISERFS (device loop0): journal params: device loop0, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 0, max trans age 30
REISERFS (device loop0): checking transaction log (loop0)
REISERFS warning (device loop0): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [1 2 0x0 SD]. This is likely to be race with knfsd. Ignore
REISERFS (device loop0): Using rupasov hash to sort names
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:3630!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 6906 Comm: syz-executor291 Not tainted 5.9.0-rc5-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011

RIP: 0010:check_journal_end fs/reiserfs/journal.c:3630 [inline]
RIP: 0010:do_journal_end+0x3698/0x48d0 fs/reiserfs/journal.c:4026
Code: fe 0a ff ff e9 51 f9 ff ff e8 94 e0 76 ff 0f 0b e8 8d e0 76 ff 0f 0b e8 86 e0 76 ff 0f 0b e8 7f e0 76 ff 0f 0b e8 78 e0 76 ff <0f> 0b e8 71 e0 76 ff 0f 0b e8 6a e0 76 ff 48 8b 44 24 08 48 8b 54
RSP: 0018:ffffc90005607a00 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffc9000570b000 RCX: ffffffff81ff2e9a
RDX: ffff8880a86485c0 RSI: ffffffff81ff5f48 RDI: 0000000000000007
RBP: 0000000000000000 R08: 0000000000000001 R09: ffffc9000570b05b
R10: 0000000000000000 R11: 0000000000000000 R12: ffffc9000570b058
R13: ffffc90005607c38 R14: 0000000000000000 R15: ffff8880a7d5a000
FS: 00007f8113e05700(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f9853cc7000 CR3: 00000000a6d1f000 CR4: 00000000001506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:

journal_end+0x277/0x320 fs/reiserfs/journal.c:3400
reiserfs_fill_super+0x20e9/0x2deb fs/reiserfs/super.c:2168
mount_bdev+0x32e/0x3f0 fs/super.c:1417
legacy_get_tree+0x105/0x220 fs/fs_context.c:592
vfs_get_tree+0x89/0x2f0 fs/super.c:1547
do_new_mount fs/namespace.c:2875 [inline]
path_mount+0x1387/0x20a0 fs/namespace.c:3192
do_mount fs/namespace.c:3205 [inline]
__do_sys_mount fs/namespace.c:3413 [inline]
__se_sys_mount fs/namespace.c:3390 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3390
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x44d45a
Code: b8 08 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 5d a1 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 3a a1 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007f8113e04bf8 EFLAGS: 00000297 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000006 RCX: 000000000044d45a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f8113e04c10
RBP: 00007f8113e04c10 R08: 00007f8113e04c50 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000297 R12: 0000000000000006
R13: 00007f8113e04c50 R14: 00007f8113e056d0 R15: 0000000000000005
Modules linked in:
---[ end trace 170160bcfcf2edcc ]---
RIP: 0010:check_journal_end fs/reiserfs/journal.c:3630 [inline]
RIP: 0010:do_journal_end+0x3698/0x48d0 fs/reiserfs/journal.c:4026
Code: fe 0a ff ff e9 51 f9 ff ff e8 94 e0 76 ff 0f 0b e8 8d e0 76 ff 0f 0b e8 86 e0 76 ff 0f 0b e8 7f e0 76 ff 0f 0b e8 78 e0 76 ff <0f> 0b e8 71 e0 76 ff 0f 0b e8 6a e0 76 ff 48 8b 44 24 08 48 8b 54
RSP: 0018:ffffc90005607a00 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffc9000570b000 RCX: ffffffff81ff2e9a
RDX: ffff8880a86485c0 RSI: ffffffff81ff5f48 RDI: 0000000000000007
RBP: 0000000000000000 R08: 0000000000000001 R09: ffffc9000570b05b
R10: 0000000000000000 R11: 0000000000000000 R12: ffffc9000570b058
R13: ffffc90005607c38 R14: 0000000000000000 R15: ffff8880a7d5a000
FS: 00007f8113e05700(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f9853c57000 CR3: 00000000a6d1f000 CR4: 00000000001506f0

[syzbot]

syzbot suspects this issue was fixed by commit:

commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <ja...@suse.cz>
Date: Wed Nov 1 17:43:10 2023 +0000

fs: Block writes to mounted block devices

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16fcca02180000
start commit: b85ea95d0864 Linux 6.7-rc1
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=b5bf1661f609e7f0
dashboard link: https://syzkaller.appspot.com/bug?extid=6820505ae5978f4f8f2f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1728c947680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1079c598e80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: fs: Block writes to mounted block devices

For information about bisection process see: https://goo.gl/tpsmEJ#bisection