[<prev] [next>] [day] [month] [year] [list]
Message-ID: <67738da6.050a0220.2f3838.04d8.GAE@google.com>
Date: Mon, 30 Dec 2024 22:22:30 -0800
From: syzbot <syzbot+a6bec34b1270dec555f4@...kaller.appspotmail.com>
To: brauner@...nel.org, ebiederm@...ssion.com, jack@...e.cz, kees@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, phillip@...ashfs.org.uk,
squashfs-devel@...ts.sourceforge.net, syzkaller-bugs@...glegroups.com,
viro@...iv.linux.org.uk
Subject: [syzbot] [squashfs?] WARNING in do_open_execat (3)
Hello,
syzbot found the following issue on:
HEAD commit: d6ef8b40d075 Merge tag 'sound-6.13-rc5' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1460c2c4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d269ef41b9262400
dashboard link: https://syzkaller.appspot.com/bug?extid=a6bec34b1270dec555f4
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152792f8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12053adf980000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-d6ef8b40.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/38a9784dd46d/vmlinux-d6ef8b40.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8d1728b3051d/bzImage-d6ef8b40.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/7dec22cf3b31/mount_2.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a6bec34b1270dec555f4@...kaller.appspotmail.com
loop0: detected capacity change from 0 to 8
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5309 at fs/exec.c:911 do_open_execat+0x376/0x480 fs/exec.c:911
Modules linked in:
CPU: 0 UID: 0 PID: 5309 Comm: syz-executor209 Not tainted 6.13.0-rc4-syzkaller-00054-gd6ef8b40d075 #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:do_open_execat+0x376/0x480 fs/exec.c:911
Code: 74 3e 49 81 ff 01 f0 ff ff 73 35 e8 74 af 86 ff 4c 89 ff e8 cc 89 fe ff eb 2b e8 65 af 86 ff e9 05 fe ff ff e8 5b af 86 ff 90 <0f> 0b 90 eb c7 e8 50 af 86 ff 48 c7 c3 e6 ff ff ff 4d 85 ff 75 c2
RSP: 0018:ffffc9000d007d00 EFLAGS: 00010293
RAX: ffffffff8218c4d5 RBX: 000000000000e000 RCX: ffff88801cfba440
RDX: 0000000000000000 RSI: 000000000000e000 RDI: 0000000000008000
RBP: ffffc9000d007dc8 R08: ffffffff8218c336 R09: 0000000000000000
R10: ffffc9000d007b60 R11: fffff52001a00f6e R12: ffffc9000d007d40
R13: 1ffff92001a00fa4 R14: ffff8880475a4578 R15: ffff88803fa8e000
FS: 0000555571145380(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff7c8c00000 CR3: 0000000043846000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
alloc_bprm+0x28/0xa30 fs/exec.c:1505
do_execveat_common+0x18c/0x6f0 fs/exec.c:1900
do_execveat fs/exec.c:2034 [inline]
__do_sys_execveat fs/exec.c:2108 [inline]
__se_sys_execveat fs/exec.c:2102 [inline]
__x64_sys_execveat+0xc4/0xe0 fs/exec.c:2102
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:0x7ff7d11e1639
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff49e02ef8 EFLAGS: 00000246 ORIG_RAX: 0000000000000142
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007ff7d11e1639
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 00000000ffffff9c
RBP: 00007ff7d1254610 R08: 0000000000001000 R09: 00007fff49e030c8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff49e030b8 R14: 0000000000000001 R15: 0000000000000001
</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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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
Powered by blists - more mailing lists