linux-kernel - [syzbot] [btrfs?] WARNING in btrfs_fileattr

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: <677a3678.050a0220.380ff0.000c.GAE@google.com>
Date: Sat, 04 Jan 2025 23:36:24 -0800
From: syzbot <syzbot+f0fd5fc4b1df37b555c2@...kaller.appspotmail.com>
To: clm@...com, dsterba@...e.com, josef@...icpanda.com, 
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [btrfs?] WARNING in btrfs_fileattr_set (2)

Hello,

syzbot found the following issue on:

HEAD commit:    ccb98ccef0e5 Merge tag 'platform-drivers-x86-v6.13-4' of g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14c2fac4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ba7cde9482d6bb6
dashboard link: https://syzkaller.appspot.com/bug?extid=f0fd5fc4b1df37b555c2
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: https://storage.googleapis.com/syzbot-assets/5813aeeed683/disk-ccb98cce.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5f3cc0826092/vmlinux-ccb98cce.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2a0638b228fb/bzImage-ccb98cce.xz

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

------------[ cut here ]------------
BTRFS: Transaction aborted (error -28)
WARNING: CPU: 1 PID: 6116 at fs/btrfs/ioctl.c:382 btrfs_fileattr_set+0xae6/0xb60 fs/btrfs/ioctl.c:382
Modules linked in:
CPU: 1 UID: 0 PID: 6116 Comm: syz.1.14 Not tainted 6.13.0-rc5-syzkaller-00004-gccb98ccef0e5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:btrfs_fileattr_set+0xae6/0xb60 fs/btrfs/ioctl.c:382
Code: 0f 8c d1 fc ff ff 48 8b 7c 24 10 e8 84 1a 3d fe e9 c2 fc ff ff e8 fa 3c d9 fd 90 48 c7 c7 c0 52 4c 8c 89 ee e8 6b e0 99 fd 90 <0f> 0b 90 90 e9 ca fd ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 84
RSP: 0018:ffffc900052bf810 EFLAGS: 00010246
RAX: 1c7144dfc1a76900 RBX: ffff888058517a68 RCX: 0000000000080000
RDX: ffffc9000dc1c000 RSI: 0000000000003a01 RDI: 0000000000003a02
RBP: 00000000ffffffe4 R08: ffffffff816019a2 R09: fffffbfff1cfa210
R10: dffffc0000000000 R11: fffffbfff1cfa210 R12: 1ffff1100b0a2f59
R13: ffff888027cbc001 R14: 0000000000000000 R15: ffff888058517ac8
FS:  00007ff8aeef06c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff8aeeeff98 CR3: 000000007cbac000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 vfs_fileattr_set+0x8ff/0xd50 fs/ioctl.c:696
 ioctl_setflags fs/ioctl.c:728 [inline]
 do_vfs_ioctl+0x2083/0x2e40 fs/ioctl.c:869
 __do_sys_ioctl fs/ioctl.c:904 [inline]
 __se_sys_ioctl+0x80/0x170 fs/ioctl.c:892
 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:0x7ff8ae185d29
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:00007ff8aeef0038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff8ae376080 RCX: 00007ff8ae185d29
RDX: 00000000200004c0 RSI: 0000000040086602 RDI: 0000000000000003
RBP: 00007ff8ae201b08 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007ff8ae376080 R15: 00007ffe81cfcfd8
 </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