linux-kernel - [syzbot] WARNING in ext4_evict

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: <000000000000daca5605d83bf62b@google.com>
Date:   Thu, 17 Feb 2022 11:42:19 -0800
From:   syzbot <syzbot+8c7921ce857a731af281@...kaller.appspotmail.com>
To:     adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        tytso@....edu
Subject: [syzbot] WARNING in ext4_evict_inode (3)

Hello,

syzbot found the following issue on:

HEAD commit:    42964a18f81c Merge tag 'objtool_urgent_for_v5.17_rc4' of g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1008ed74700000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5707221760c00a20
dashboard link: https://syzkaller.appspot.com/bug?extid=8c7921ce857a731af281
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

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

------------[ cut here ]------------
WARNING: CPU: 2 PID: 3682 at fs/ext4/inode.c:231 ext4_evict_inode+0xf9a/0x1950 fs/ext4/inode.c:231
Modules linked in:
CPU: 2 PID: 3682 Comm: syz-executor.2 Not tainted 5.17.0-rc3-syzkaller-00329-g42964a18f81c #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
RIP: 0010:ext4_evict_inode+0xf9a/0x1950 fs/ext4/inode.c:231
Code: 28 41 bc 01 00 00 00 48 89 04 24 e9 62 f6 ff ff c7 44 24 24 06 00 00 00 c7 44 24 20 06 00 00 00 e9 e1 f6 ff ff e8 36 25 63 ff <0f> 0b e9 c8 f5 ff ff e8 fa 23 aa ff e9 60 f1 ff ff 48 89 cf e8 ed
RSP: 0018:ffffc9000276fc98 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 1ffff920004edf99 RCX: 0000000000000000
RDX: ffff88805e45e2c0 RSI: ffffffff8214ddea RDI: 0000000000000003
RBP: ffff8880235bf6a0 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff8214d3b0 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000001 R14: ffff88801acac830 R15: ffff888026d92728
FS:  00005555566dc400(0000) GS:ffff88802cb00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555565fb708 CR3: 000000005e443000 CR4: 0000000000150ee0
Call Trace:
 <TASK>
 evict+0x2ed/0x6b0 fs/inode.c:664
 iput_final fs/inode.c:1744 [inline]
 iput.part.0+0x562/0x820 fs/inode.c:1770
 iput+0x58/0x70 fs/inode.c:1760
 do_unlinkat+0x418/0x650 fs/namei.c:4225
 __do_sys_unlink fs/namei.c:4266 [inline]
 __se_sys_unlink fs/namei.c:4264 [inline]
 __x64_sys_unlink+0xc6/0x110 fs/namei.c:4264
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f1762356997
Code: 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 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:00007ffca9eba208 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1762356997
RDX: 00007ffca9eba240 RSI: 00007ffca9eba240 RDI: 00007ffca9eba2d0
RBP: 00007ffca9eba2d0 R08: 0000000000000001 R09: 00007ffca9eba0a0
R10: 00005555566dd903 R11: 0000000000000206 R12: 00007f17623b01ea
R13: 00007ffca9ebb390 R14: 00005555566dd810 R15: 00007ffca9ebb3d0
 </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.