linux-kernel - [syzbot] [gfs2?] WARNING in rgblk

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: <000000000000251ced0621e8d78d@google.com>
Date: Thu, 12 Sep 2024 02:36:25 -0700
From: syzbot <syzbot+363090afa6ba1357e375@...kaller.appspotmail.com>
To: agruenba@...hat.com, gfs2@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [gfs2?] WARNING in rgblk_free

Hello,

syzbot found the following issue on:

HEAD commit:    7c6a3a65ace7 minmax: reduce min/max macro expansion in ato..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167d5807980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=61d235cb8d15001c
dashboard link: https://syzkaller.appspot.com/bug?extid=363090afa6ba1357e375
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-7c6a3a65.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1a9a78c56595/vmlinux-7c6a3a65.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b4e1f2187a1/bzImage-7c6a3a65.xz

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

loop0: detected capacity change from 0 to 32768
gfs2: fsid=syz:syz: Trying to join cluster "lock_nolock", "syz:syz"
gfs2: fsid=syz:syz: Now mounting FS (format 1801)...
gfs2: fsid=syz:syz.0: journal 0 mapped with 1 extents in 2ms
gfs2: fsid=syz:syz.0: first mount done, others may mount
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5117 at fs/gfs2/rgrp.c:2269 rgblk_free+0x1f5/0x960 fs/gfs2/rgrp.c:2269
Modules linked in:
CPU: 0 UID: 0 PID: 5117 Comm: syz.0.0 Not tainted 6.11.0-rc7-syzkaller-00021-g7c6a3a65ace7 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:rgblk_free+0x1f5/0x960 fs/gfs2/rgrp.c:2269
Code: 20 84 c0 0f 85 fc 06 00 00 8b 1b 89 df 44 89 ee e8 d0 d5 ac fd 44 39 eb 76 60 e8 06 d4 ac fd e9 e0 00 00 00 e8 fc d3 ac fd 90 <0f> 0b 90 49 bc 00 00 00 00 00 fc ff df 48 c7 84 24 80 00 00 00 0e
RSP: 0018:ffffc90002faf420 EFLAGS: 00010283
RAX: ffffffff83e6b7a8 RBX: ffff888000cd4028 RCX: 0000000000040000
RDX: ffffc9000b8d2000 RSI: 000000000000a5db RDI: 000000000000a5dc
RBP: ffffc90002faf530 R08: ffffffff83e6b79e R09: 1ffffffff2030ebd
R10: dffffc0000000000 R11: fffffbfff2030ebe R12: 0000000000090047
R13: 00000000000024a4 R14: dffffc0000000000 R15: ffff888000cd4000
FS:  00007fb62c0a76c0(0000) GS:ffff88801fe00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb62c067470 CR3: 0000000035656000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __gfs2_free_blocks fs/gfs2/rgrp.c:2525 [inline]
 gfs2_free_meta+0x99/0x280 fs/gfs2/rgrp.c:2552
 ea_dealloc_unstuffed+0x7cf/0xb00 fs/gfs2/xattr.c:303
 ea_remove_unstuffed fs/gfs2/xattr.c:342 [inline]
 ea_set_remove_unstuffed+0x1cb/0x290 fs/gfs2/xattr.c:1086
 __gfs2_xattr_set+0x6f8/0xcf0 fs/gfs2/xattr.c:1217
 gfs2_xattr_set+0x35d/0x460 fs/gfs2/xattr.c:1258
 __vfs_setxattr+0x468/0x4a0 fs/xattr.c:200
 __vfs_setxattr_noperm+0x12e/0x660 fs/xattr.c:234
 vfs_setxattr+0x221/0x430 fs/xattr.c:321
 do_setxattr fs/xattr.c:629 [inline]
 path_setxattr+0x37e/0x4d0 fs/xattr.c:658
 __do_sys_setxattr fs/xattr.c:676 [inline]
 __se_sys_setxattr fs/xattr.c:672 [inline]
 __x64_sys_setxattr+0xbb/0xd0 fs/xattr.c:672
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb62b37def9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb62c0a7038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fb62b535f80 RCX: 00007fb62b37def9
RDX: 00000000200001c0 RSI: 0000000020000180 RDI: 00000000200000c0
RBP: 00007fb62b3f0b76 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000011 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fb62b535f80 R15: 00007fff806d2368
 </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