linux-kernel - Re: [syzbot] upstream boot error: BUG: corrupted list in new

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 15 Aug 2022 11:07:15 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     syzbot <syzbot+24df94a8d05d5a3e68f0@...kaller.appspotmail.com>
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: Re: [syzbot] upstream boot error: BUG: corrupted list in new_inode

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git  fc4d146e8d7d25ef88d409bea1f2e9aff7f30635

On Mon, Aug 15, 2022 at 11:00:29AM -0700, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    5d6a0f4da927 Merge tag 'for-linus-6.0-rc1b-tag' of git://g..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1399b2f3080000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=f6bcb425ba129b87
> dashboard link: https://syzkaller.appspot.com/bug?extid=24df94a8d05d5a3e68f0
> compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+24df94a8d05d5a3e68f0@...kaller.appspotmail.com
> 
> list_add corruption. next->prev should be prev (ffff8881401c0a00), but was ffff000000000000. (next=ffff88801fb50308).
> ------------[ cut here ]------------
> kernel BUG at lib/list_debug.c:27!
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 24 Comm: kdevtmpfs Not tainted 5.19.0-syzkaller-14374-g5d6a0f4da927 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
> RIP: 0010:__list_add_valid.cold+0xf/0x58 lib/list_debug.c:27
> Code: 48 c7 c6 00 ec 48 8a 48 89 ef 49 c7 c7 ea ff ff ff e8 5b 63 05 00 e9 c2 7d b6 fa 4c 89 e1 48 c7 c7 a0 f2 48 8a e8 95 f2 f0 ff <0f> 0b 48 c7 c7 40 f2 48 8a e8 87 f2 f0 ff 0f 0b 48 c7 c7 a0 f1 48
> RSP: 0018:ffffc900001efc10 EFLAGS: 00010286
> RAX: 0000000000000075 RBX: ffff8881401c0000 RCX: 0000000000000000
> RDX: ffff888012620000 RSI: ffffffff8161f148 RDI: fffff5200003df74
> RBP: ffff88801db8b588 R08: 0000000000000075 R09: 0000000000000000
> R10: 0000000080000001 R11: 0000000000000000 R12: ffff88801fb50308
> R13: ffff88801fb50308 R14: ffff8881401c0000 R15: ffff88801db8b588
> FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffff88823ffff000 CR3: 000000000bc8e000 CR4: 0000000000350ef0
> Call Trace:
>  <TASK>
>  __list_add include/linux/list.h:69 [inline]
>  list_add include/linux/list.h:88 [inline]
>  inode_sb_list_add fs/inode.c:495 [inline]
>  new_inode+0x114/0x270 fs/inode.c:1049
>  shmem_get_inode+0x19b/0xe00 mm/shmem.c:2306
>  shmem_mknod+0x5a/0x1f0 mm/shmem.c:2873
>  vfs_mknod+0x4d2/0x7e0 fs/namei.c:3892
>  handle_create+0x340/0x4b3 drivers/base/devtmpfs.c:226
>  handle drivers/base/devtmpfs.c:391 [inline]
>  devtmpfs_work_loop drivers/base/devtmpfs.c:406 [inline]
>  devtmpfsd+0x1a4/0x2a3 drivers/base/devtmpfs.c:448
>  kthread+0x2e4/0x3a0 kernel/kthread.c:376
>  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
>  </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:__list_add_valid.cold+0xf/0x58 lib/list_debug.c:27
> Code: 48 c7 c6 00 ec 48 8a 48 89 ef 49 c7 c7 ea ff ff ff e8 5b 63 05 00 e9 c2 7d b6 fa 4c 89 e1 48 c7 c7 a0 f2 48 8a e8 95 f2 f0 ff <0f> 0b 48 c7 c7 40 f2 48 8a e8 87 f2 f0 ff 0f 0b 48 c7 c7 a0 f1 48
> RSP: 0018:ffffc900001efc10 EFLAGS: 00010286
> RAX: 0000000000000075 RBX: ffff8881401c0000 RCX: 0000000000000000
> RDX: ffff888012620000 RSI: ffffffff8161f148 RDI: fffff5200003df74
> RBP: ffff88801db8b588 R08: 0000000000000075 R09: 0000000000000000
> R10: 0000000080000001 R11: 0000000000000000 R12: ffff88801fb50308
> R13: ffff88801fb50308 R14: ffff8881401c0000 R15: ffff88801db8b588
> FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffff88823ffff000 CR3: 000000000bc8e000 CR4: 0000000000350ef0
> 
> 
> ---
> 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.