Re: [Cluster-devel] [syzbot] WARNING in ovs_dp_reset_user_features
On Wed, 2022-10-12 at 10:43 -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:e8bc52cb8df8 Merge tag 'driver-core-6.1-rc1' of git://git...
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=134de04288
> kernel config: https://syzkaller.appspot.com/x/.config?x=7579993da6496f03
> dashboard link: https://syzkaller.appspot.com/bug?extid=31cde0bef4bbf8ba2d86
> compiler: Debian clang version
> 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU
> Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12173a3488
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1792461a88
>
> Downloadable assets:
> disk image:
> https://storage.googleapis.com/syzbot-assets/4dc25a89bfbd/disk-e8bc52cb.raw.xz
> vmlinux:
> https://storage.googleapis.com/syzbot-assets/16c9ca5fd754/vmlinux-e8bc52cb.xz
>
> The issue was bisected to:
>
> commit 6b0afc0cc3e9a9a91f5a76d0965d449781441e18
> Author: Alexander Aring
> Date: Wed Jun 22 18:45:23 2022 +
>
> fs: dlm: don't use deprecated timeout features by default
This commit is not really relevant for the issue, but it makes the
reproducer fail, since it changes the genl_family registration order
and the repro hard-codes the ovs genl family id.
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10d5787c88
> final oops: https://syzkaller.appspot.com/x/report.txt?x=12d5787c88
> console output: https://syzkaller.appspot.com/x/log.txt?x=14d5787c88
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+31cde0bef4bbf8ba2...@syzkaller.appspotmail.com
> Fixes: 6b0afc0cc3e9 ("fs: dlm: don't use deprecated timeout features by
> default")
>
> [ cut here ]
> Dropping previously announced user features
> WARNING: CPU: 1 PID: 3608 at net/openvswitch/datapath.c:1619
> ovs_dp_reset_user_features+0x1bc/0x240 net/openvswitch/datapath.c:1619
> Modules linked in:
> CPU: 1 PID: 3608 Comm: syz-executor162 Not tainted
> 6.0.0-syzkaller-07994-ge8bc52cb8df8 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 09/22/2022
> RIP: 0010:ovs_dp_reset_user_features+0x1bc/0x240
> net/openvswitch/datapath.c:1619
> Code: 00 c7 03 00 00 00 00 eb 05 e8 d0 be 67 f7 5b 41 5c 41 5e 41 5f 5d c3 e8
> c2 be 67 f7 48 c7 c7 00 92 e3 8b 31 c0 e8 74 7a 2f f7 <0f> 0b eb c7 44 89 f1
> 80 e1 07 fe c1 38 c1 0f 8c f1 fe ff ff 4c 89
> RSP: 0018:c90003b8f370 EFLAGS: 00010246
> RAX: e794c0e413340e00 RBX: 8880175cae68 RCX: 88801c069d80
> RDX: RSI: 8000 RDI:
> RBP: 0008 R08: 816c58ad R09: ed1017364f13
> R10: ed1017364f13 R11: 111017364f12 R12: dc00
> R13: 8880175ca450 R14: 111002eb95cd R15: c90003b8f6b0
> FS: 57276300() GS:8880b9b0() knlGS:
> CS: 0010 DS: ES: CR0: 80050033
> CR2: 2916 CR3: 1ed81000 CR4: 003506e0
> DR0: DR1: DR2:
> DR3: DR6: fffe0ff0 DR7: 0400
> Call Trace:
>
> ovs_dp_cmd_new+0x8f6/0xc80 net/openvswitch/datapath.c:1822
> genl_family_rcv_msg_doit net/netlink/genetlink.c:731 [inline]
> genl_family_rcv_msg net/netlink/genetlink.c:808 [inline]
> genl_rcv_msg+0x11ca/0x1670 net/netlink/genetlink.c:825
> netlink_rcv_skb+0x1f0/0x460 net/netlink/af_netlink.c:2540
> genl_rcv+0x24/0x40 net/netlink/genetlink.c:836
> netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
> netlink_unicast+0x7e7/0x9c0 net/netlink/af_netlink.c:1345
> netlink_sendmsg+0x9b3/0xcd0 net/netlink/af_netlink.c:1921
> sock_sendmsg_nosec net/socket.c:714 [inline]
> sock_sendmsg net/socket.c:734 [inline]
> sys_sendmsg+0x597/0x8e0 net/socket.c:2482
> ___sys_sendmsg net/socket.c:2536 [inline]
> __sys_sendmsg+0x28e/0x390 net/socket.c:2565
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
> RIP: 0033:0x7fc51f29de89
> Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 14 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 c0 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:7ffd99ec6ed8 EFLAGS: 0246 ORIG_RAX: 002e
> RAX: ffda RBX: a2c4 RCX: 7fc51f29de89
> RDX: RSI: 2100 RDI: 0003
> RBP: R08: 7ffd99ec7078 R09: 7ffd99ec7078
> R10: 7ffd99ec6950 R11: 0246 R12: 7ffd99ec6eec
> R13: 431bde82d7b634db R14: R15:
>
>
In this specific case it looks like the warning is caused by the fact
that ovs allows an 'outdated' datapath to set u
[Cluster-devel] [syzbot] WARNING in ovs_dp_reset_user_features
Hello,
syzbot found the following issue on:
HEAD commit:e8bc52cb8df8 Merge tag 'driver-core-6.1-rc1' of git://git...
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=134de04288
kernel config: https://syzkaller.appspot.com/x/.config?x=7579993da6496f03
dashboard link: https://syzkaller.appspot.com/bug?extid=31cde0bef4bbf8ba2d86
compiler: Debian clang version
13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU
Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12173a3488
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1792461a88
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/4dc25a89bfbd/disk-e8bc52cb.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/16c9ca5fd754/vmlinux-e8bc52cb.xz
The issue was bisected to:
commit 6b0afc0cc3e9a9a91f5a76d0965d449781441e18
Author: Alexander Aring
Date: Wed Jun 22 18:45:23 2022 +
fs: dlm: don't use deprecated timeout features by default
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10d5787c88
final oops: https://syzkaller.appspot.com/x/report.txt?x=12d5787c88
console output: https://syzkaller.appspot.com/x/log.txt?x=14d5787c88
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+31cde0bef4bbf8ba2...@syzkaller.appspotmail.com
Fixes: 6b0afc0cc3e9 ("fs: dlm: don't use deprecated timeout features by
default")
[ cut here ]
Dropping previously announced user features
WARNING: CPU: 1 PID: 3608 at net/openvswitch/datapath.c:1619
ovs_dp_reset_user_features+0x1bc/0x240 net/openvswitch/datapath.c:1619
Modules linked in:
CPU: 1 PID: 3608 Comm: syz-executor162 Not tainted
6.0.0-syzkaller-07994-ge8bc52cb8df8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google
09/22/2022
RIP: 0010:ovs_dp_reset_user_features+0x1bc/0x240 net/openvswitch/datapath.c:1619
Code: 00 c7 03 00 00 00 00 eb 05 e8 d0 be 67 f7 5b 41 5c 41 5e 41 5f 5d c3 e8
c2 be 67 f7 48 c7 c7 00 92 e3 8b 31 c0 e8 74 7a 2f f7 <0f> 0b eb c7 44 89 f1 80
e1 07 fe c1 38 c1 0f 8c f1 fe ff ff 4c 89
RSP: 0018:c90003b8f370 EFLAGS: 00010246
RAX: e794c0e413340e00 RBX: 8880175cae68 RCX: 88801c069d80
RDX: RSI: 8000 RDI:
RBP: 0008 R08: 816c58ad R09: ed1017364f13
R10: ed1017364f13 R11: 111017364f12 R12: dc00
R13: 8880175ca450 R14: 111002eb95cd R15: c90003b8f6b0
FS: 57276300() GS:8880b9b0() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 2916 CR3: 1ed81000 CR4: 003506e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
ovs_dp_cmd_new+0x8f6/0xc80 net/openvswitch/datapath.c:1822
genl_family_rcv_msg_doit net/netlink/genetlink.c:731 [inline]
genl_family_rcv_msg net/netlink/genetlink.c:808 [inline]
genl_rcv_msg+0x11ca/0x1670 net/netlink/genetlink.c:825
netlink_rcv_skb+0x1f0/0x460 net/netlink/af_netlink.c:2540
genl_rcv+0x24/0x40 net/netlink/genetlink.c:836
netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
netlink_unicast+0x7e7/0x9c0 net/netlink/af_netlink.c:1345
netlink_sendmsg+0x9b3/0xcd0 net/netlink/af_netlink.c:1921
sock_sendmsg_nosec net/socket.c:714 [inline]
sock_sendmsg net/socket.c:734 [inline]
sys_sendmsg+0x597/0x8e0 net/socket.c:2482
___sys_sendmsg net/socket.c:2536 [inline]
__sys_sendmsg+0x28e/0x390 net/socket.c:2565
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc51f29de89
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 14 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:7ffd99ec6ed8 EFLAGS: 0246 ORIG_RAX: 002e
RAX: ffda RBX: a2c4 RCX: 7fc51f29de89
RDX: RSI: 2100 RDI: 0003
RBP: R08: 7ffd99ec7078 R09: 7ffd99ec7078
R10: 7ffd99ec6950 R11: 0246 R12: 7ffd99ec6eec
R13: 431bde82d7b634db R14: R15:
---
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 syzkal...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
[Cluster-devel] [syzbot] UBSAN: shift-out-of-bounds in gfs2_getbuf
Hello, syzbot found the following issue on: HEAD commit:493ffd6605b2 Merge tag 'ucount-rlimits-cleanups-for-v5.19'.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1462025288 kernel config: https://syzkaller.appspot.com/x/.config?x=d19f5d16783f901 dashboard link: https://syzkaller.appspot.com/bug?extid=87a187973530ac822e3c compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/f1ff6481e26f/disk-493ffd66.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/101bd3c7ae47/vmlinux-493ffd66.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+87a187973530ac822...@syzkaller.appspotmail.com UBSAN: shift-out-of-bounds in fs/gfs2/meta_io.c:128:16 shift exponent 4294967293 is too large for 64-bit type 'u64' (aka 'unsigned long long') CPU: 0 PID: 10195 Comm: syz-executor.3 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_shift_out_of_bounds+0x33d/0x3b0 lib/ubsan.c:322 gfs2_getbuf+0x759/0x7d0 fs/gfs2/meta_io.c:128 gfs2_meta_read+0x153/0x910 fs/gfs2/meta_io.c:265 gfs2_meta_buffer+0x153/0x3a0 fs/gfs2/meta_io.c:491 gfs2_meta_inode_buffer fs/gfs2/meta_io.h:72 [inline] gfs2_inode_refresh+0xab/0xe90 fs/gfs2/glops.c:472 gfs2_instantiate+0x15e/0x220 fs/gfs2/glock.c:515 gfs2_glock_holder_ready fs/gfs2/glock.c:1303 [inline] gfs2_glock_wait+0x1d9/0x2a0 fs/gfs2/glock.c:1323 gfs2_glock_nq_init fs/gfs2/glock.h:263 [inline] gfs2_lookupi+0x40c/0x650 fs/gfs2/inode.c:306 gfs2_lookup_simple+0xec/0x170 fs/gfs2/inode.c:258 init_journal+0x19b/0x22c0 fs/gfs2/ops_fstype.c:739 init_inodes+0xdc/0x340 fs/gfs2/ops_fstype.c:882 gfs2_fill_super+0x1ad8/0x2610 fs/gfs2/ops_fstype.c:1240 get_tree_bdev+0x400/0x620 fs/super.c:1323 gfs2_get_tree+0x50/0x210 fs/gfs2/ops_fstype.c:1323 vfs_get_tree+0x88/0x270 fs/super.c:1530 do_new_mount+0x289/0xad0 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f0eed68cada Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:7f0eee73cf88 EFLAGS: 0202 ORIG_RAX: 00a5 RAX: ffda RBX: 2200 RCX: 7f0eed68cada RDX: 2000 RSI: 2100 RDI: 7f0eee73cfe0 RBP: 7f0eee73d020 R08: 7f0eee73d020 R09: 2000 R10: 0008 R11: 0202 R12: 2000 R13: 2100 R14: 7f0eee73cfe0 R15: 2080 --- 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 syzkal...@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Re: [Cluster-devel] [syzbot] UBSAN: shift-out-of-bounds in gfs2_getbuf
On 13/10/2022 14:31, syzbot wrote: Hello, syzbot found the following issue on: HEAD commit:493ffd6605b2 Merge tag 'ucount-rlimits-cleanups-for-v5.19'.. $ git describe --contains 493ffd6605b2 next-20221011~172 git tree: upstream It would be useful to know the precise git tree. console output: https://syzkaller.appspot.com/x/log.txt?x=1462025288 kernel config: https://syzkaller.appspot.com/x/.config?x=d19f5d16783f901 dashboard link: https://syzkaller.appspot.com/bug?extid=87a187973530ac822e3c compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/f1ff6481e26f/disk-493ffd66.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/101bd3c7ae47/vmlinux-493ffd66.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+87a187973530ac822...@syzkaller.appspotmail.com UBSAN: shift-out-of-bounds in fs/gfs2/meta_io.c:128:16 shift = PAGE_SHIFT - sdp->sd_sb.sb_bsize_shift; index = blkno >> shift; /* convert block to page */ bufnum = blkno - (index << shift); /* block buf index within page */ So likely fixed by commit 670f8ce56dd0632dc29a0322e188cc73ce3c6b92 "gfs2: Check sb_bsize_shift after reading superblock" which has just been merged into mainline, but doesn't appear in next-20221011~172 Andy shift exponent 4294967293 is too large for 64-bit type 'u64' (aka 'unsigned long long') CPU: 0 PID: 10195 Comm: syz-executor.3 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_shift_out_of_bounds+0x33d/0x3b0 lib/ubsan.c:322 gfs2_getbuf+0x759/0x7d0 fs/gfs2/meta_io.c:128 gfs2_meta_read+0x153/0x910 fs/gfs2/meta_io.c:265 gfs2_meta_buffer+0x153/0x3a0 fs/gfs2/meta_io.c:491 gfs2_meta_inode_buffer fs/gfs2/meta_io.h:72 [inline] gfs2_inode_refresh+0xab/0xe90 fs/gfs2/glops.c:472 gfs2_instantiate+0x15e/0x220 fs/gfs2/glock.c:515 gfs2_glock_holder_ready fs/gfs2/glock.c:1303 [inline] gfs2_glock_wait+0x1d9/0x2a0 fs/gfs2/glock.c:1323 gfs2_glock_nq_init fs/gfs2/glock.h:263 [inline] gfs2_lookupi+0x40c/0x650 fs/gfs2/inode.c:306 gfs2_lookup_simple+0xec/0x170 fs/gfs2/inode.c:258 init_journal+0x19b/0x22c0 fs/gfs2/ops_fstype.c:739 init_inodes+0xdc/0x340 fs/gfs2/ops_fstype.c:882 gfs2_fill_super+0x1ad8/0x2610 fs/gfs2/ops_fstype.c:1240 get_tree_bdev+0x400/0x620 fs/super.c:1323 gfs2_get_tree+0x50/0x210 fs/gfs2/ops_fstype.c:1323 vfs_get_tree+0x88/0x270 fs/super.c:1530 do_new_mount+0x289/0xad0 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f0eed68cada Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:7f0eee73cf88 EFLAGS: 0202 ORIG_RAX: 00a5 RAX: ffda RBX: 2200 RCX: 7f0eed68cada RDX: 2000 RSI: 2100 RDI: 7f0eee73cfe0 RBP: 7f0eee73d020 R08: 7f0eee73d020 R09: 2000 R10: 0008 R11: 0202 R12: 2000 R13: 2100 R14: 7f0eee73cfe0 R15: 2080 --- 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 syzkal...@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Re: [Cluster-devel] [syzbot] UBSAN: shift-out-of-bounds in gfs2_getbuf
syzbot has found a reproducer for the following issue on: HEAD commit:55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g.. git tree: upstream console+strace: https://syzkaller.appspot.com/x/log.txt?x=176500c288 kernel config: https://syzkaller.appspot.com/x/.config?x=c29b6436e994d72e dashboard link: https://syzkaller.appspot.com/bug?extid=87a187973530ac822e3c compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=174eb6aa88 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1118d5a488 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/c8f5131ab57d/disk-55be6084.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/77167f226f35/vmlinux-55be6084.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/930c28d03062/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+87a187973530ac822...@syzkaller.appspotmail.com loop0: detected capacity change from 0 to 264192 gfs2: fsid=loop0: Trying to join cluster "lock_nolock", "loop0" gfs2: fsid=loop0: Now mounting FS (format 1801)... UBSAN: shift-out-of-bounds in fs/gfs2/meta_io.c:128:16 shift exponent 4294967293 is too large for 64-bit type 'u64' (aka 'unsigned long long') CPU: 1 PID: 3612 Comm: syz-executor373 Not tainted 6.0.0-syzkaller-09589-g55be6084c8e0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_shift_out_of_bounds+0x3a6/0x420 lib/ubsan.c:322 gfs2_getbuf+0x759/0x7d0 fs/gfs2/meta_io.c:128 gfs2_meta_read+0x16a/0x910 fs/gfs2/meta_io.c:265 gfs2_meta_buffer+0x195/0x400 fs/gfs2/meta_io.c:491 gfs2_meta_inode_buffer fs/gfs2/meta_io.h:72 [inline] gfs2_inode_refresh+0xd6/0xdc0 fs/gfs2/glops.c:472 gfs2_instantiate+0x15e/0x220 fs/gfs2/glock.c:515 gfs2_glock_holder_ready fs/gfs2/glock.c:1303 [inline] gfs2_glock_wait+0x1d9/0x2a0 fs/gfs2/glock.c:1323 gfs2_glock_nq_init fs/gfs2/glock.h:263 [inline] gfs2_lookupi+0x411/0x5f0 fs/gfs2/inode.c:306 gfs2_lookup_simple+0xec/0x170 fs/gfs2/inode.c:258 init_journal+0x1c3/0x2310 fs/gfs2/ops_fstype.c:739 init_inodes+0xdc/0x340 fs/gfs2/ops_fstype.c:882 gfs2_fill_super+0x1be3/0x2710 fs/gfs2/ops_fstype.c:1240 get_tree_bdev+0x400/0x620 fs/super.c:1323 gfs2_get_tree+0x50/0x210 fs/gfs2/ops_fstype.c:1323 vfs_get_tree+0x88/0x270 fs/super.c:1530 do_new_mount+0x289/0xad0 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f7caad9342a Code: 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:7ffc97eb3c68 EFLAGS: 0282 ORIG_RAX: 00a5 RAX: ffda RBX: 0003 RCX: 7f7caad9342a RDX: 2000 RSI: 2100 RDI: 7ffc97eb3c80 RBP: 7ffc97eb3c80 R08: 7ffc97eb3cc0 R09: 56b512c0 R10: 0008 R11: 0282 R12: 0004 R13: 7ffc97eb3cc0 R14: 0001 R15: 2218
