From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id A18EFC77B61 for ; Mon, 24 Apr 2023 08:11:40 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 3ED106B0074; Mon, 24 Apr 2023 04:11:40 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 39CEC6B0075; Mon, 24 Apr 2023 04:11:40 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 264926B0078; Mon, 24 Apr 2023 04:11:40 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 166386B0074 for ; Mon, 24 Apr 2023 04:11:40 -0400 (EDT) Received: from smtpin16.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id B1E121A026D for ; Mon, 24 Apr 2023 08:11:39 +0000 (UTC) X-FDA: 80715565518.16.7157176 Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) by imf23.hostedemail.com (Postfix) with ESMTP id 0F6F0140017 for ; Mon, 24 Apr 2023 08:11:37 +0000 (UTC) Authentication-Results: imf23.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf23.hostedemail.com: domain of 3uTlGZAkbAG4eklWMXXQdMbbUP.SaaSXQgeQdOaZfQZf.OaY@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.199 as permitted sender) smtp.mailfrom=3uTlGZAkbAG4eklWMXXQdMbbUP.SaaSXQgeQdOaZfQZf.OaY@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1682323898; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding:in-reply-to: references; bh=la37d+qfPeKJVd2GQq3nMgGF4BXmkpQNTs8xfb02sr0=; b=iQSNIN7oik3I4UaPylkwx/wU14RaD0+L/CYT9JEu2xCIZOL7rD+vwY1pHNEwerp9m83Hdu rbyt0qnN2pkNYwZ3+ovqnF4a6WS2UVuzBHnSgvzQsIsNATUQK9TMR+RoQmXYcNYfgM+xPh 77Sz/66IXjSzlsR1295/uUhC0KaXz34= ARC-Authentication-Results: i=1; imf23.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf23.hostedemail.com: domain of 3uTlGZAkbAG4eklWMXXQdMbbUP.SaaSXQgeQdOaZfQZf.OaY@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.199 as permitted sender) smtp.mailfrom=3uTlGZAkbAG4eklWMXXQdMbbUP.SaaSXQgeQdOaZfQZf.OaY@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1682323898; a=rsa-sha256; cv=none; b=F75Yb2EV7X4CbGp3Gqf04J2ViKlPejbrSajqojYUZZSCgjdk0f8wDn18c/wzFVGqCQCGTi pHPZ8JwzUecrqr4yed560qklvKwzueDhfPkYTXIbeBI5NGu/w1jBvACgptgqTTg5OjOK0E MM8J8YzTzoqIhk0i0TI4Udg9XAmXNjM= Received: by mail-il1-f199.google.com with SMTP id e9e14a558f8ab-32addcf3a73so158841405ab.0 for ; Mon, 24 Apr 2023 01:11:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682323897; x=1684915897; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=la37d+qfPeKJVd2GQq3nMgGF4BXmkpQNTs8xfb02sr0=; b=cER0kcKIcXa7AAVqeTBXdooXOHwTbJkONkVlF5KBVTBhuofFYBsactqHKzo/Wl/AzA lFdkaTBfKn94eBl8WUIodUo4vQXagfwDuVWgnkeIolcgQE2dbspUaJC+TqFMW/x4KkYR 5KIc28/9bLEubpJrWbdZPktWeO+52s+MgpXhoMqcn8ioVdvTahc7pS3SlSubEjymchLg lQv9WQ+aq1epuT9RxaCmzPdavbSX9JBpex4Obi0WzTlu7YJBywr1n35E788qbBl2oHv8 5CbTVWFRi/9Oa3dJz/RZOC4QDHSKE28/kTaujrkp83L/Hz5u1A45GJ0vK2ZRjYOoswxR rLww== X-Gm-Message-State: AAQBX9fR6xIbuLHSUokxndqwTCosVHgFaDKqBIAWGyzmQDXvTXQnRpad 2VfSS+JJt7DJ8y8yAscOj5iOYUyeXLVMScTaw5VQowfNQ7mW X-Google-Smtp-Source: AKy350ZqU5Bed8pxPoOPyzjcqzZoYYhNb5ceSd8Uf+oAdrTomw2mMygTIRTlvnmvguaMZx21hftKFdQ/mCDf3CTxIWHEHDpnZV2B MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1d0b:b0:32b:fc:52b1 with SMTP id i11-20020a056e021d0b00b0032b00fc52b1mr5819575ila.0.1682323897343; Mon, 24 Apr 2023 01:11:37 -0700 (PDT) Date: Mon, 24 Apr 2023 01:11:37 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000004c66b405fa108e27@google.com> Subject: [syzbot] [fs?] [mm?] possible deadlock in do_writepages From: syzbot To: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, willy@infradead.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 0F6F0140017 X-Rspam-User: X-Stat-Signature: big9xku8j63ydfqt5711au8yixyhnj9u X-HE-Tag: 1682323897-522100 X-HE-Meta: U2FsdGVkX1/ERRxhkwOFE4lZ9oUObxTckevV58lFq7yzRadHtaNpevDV4TnTcV+wIdHhrn1YV9ZVNhQGOu4/BhmLGg5ySOCOBjg0oldb7Q4WEtbvZ0K0bokgfevUrct85ONlU6vc0awEKxFbyqFkPhDAqXfg/Jmm2SFyGRZMJG/13zz7/XMCtXLQJzzuL+sV0Q4ZI4CIyOLWA2j4riinfzRZyDUj9M5DgddawUJh1kmEqFwY9wSnlCUFJES4vEYrEhHiRSjY0o1z7EY5bZYYSmNUBw/JKUm8CTxO94260GHHCwZny6ra+6eFngFl7HE3Hd8hihPoHbR26q0Dt94dbvuAkRxIUh8Cn2x1fle2O4mpDCJlTkjbU0gapxbYQ8Y2FwkSvceOF1mLl/e6TMa3gnUeSF7Ko6IZmsbcEmMyokqBN1EacNj0tAEPW8R9JFjdhBN/PKBbmER5R09Ov6nHIofuP6s8PsaD5xQRkLuMqX/+gfETg/j/HbyGO+/OxSuBNswzzh2Y/0Ug+5sHPgGKn+ENHtqyJxN38/t6b3KtOt+ft50dZkclaL2cw29nofxxPRgKsm/cbpT9PCEvh6pVUYXUC7EMU9OMMd9ULIWmLwj/vH2vVgQA3Taqg1SMVnlZfYzfLPf2oVLcRD435SHyU81bMO7VryDwxgThtyJNhaOyiJrLqPJFa0xFkhU7IYyyhRMx4AAGSWr3VMh7VhNhvw9AtVde5xH9in1gQBq/s/tCc6vC3oFrbJRJHkSeCDdGzHaMrn2Zf62zPY9H0MTy60jLeL59KBxhLE5A5kstpCuYzia01o+nDxHlwWr2hvzLGTbxplIPf/+bIQIwNBQhPuVtr27j9SbGawwzi+rDqN0EN0H+wLO3wBsshpzin1ZtcmtgJ+814CO3mRwfAYnMlu0OMahOdJ8raHiqK8DLcS9TIXIdAiZplumAxM7AILpzmWZq+D1/KvGkaz3/LUa gWSSOeOc Gn0+I5kJ6Za7Ur4TqqhwIutCrFRluvfBUtpyV94iVCfroC3wtGhaHtxWo/KoBFUluv8xp7jKjaa0dUyUVaOtuHcKKrAZ+TP+oFoeFroJ25TzRf/CAIw2/37tFCywUGfT+TFUIitJ1Q+SVfmH6FQI0NUGXHrFpkmyiJICU7Cc4a02jmelZxpfJyZNNAVQ6VzEYWZ9aNOt1TIRaHEbY/QS58CX/aJBTGaNoyqldvYLkEu9CyIXtc2u2Zl7/3omA4RTwQcW28LoErK83rbrAhlcFB+jAmbw4hRc3H3D9L1tn17ASmiWq9EEs6snRGHWxuhqDLBZbOOh06N+EnTMxsq12Jz4n+Co+rPpckjXEIFrORSXlUIKNcU9XWNbhEXVSA6VkbShHv8GBcVuuzftEHinxVAVV/lOOhMn9fP9Ju5MQsRSXX8bdqTptcbSwqo/HHTa01/MtaO4tkOK8kzgrh5cihzADlMpy5MR/HRqp6qa82tUWgOvmCHq3kkExKFmdzwIyjxR/e1yHh63wIyNncq46dwZTfwk4wpT/zplnQ+rMnF7VrA5dtF5debCfCWtAXj8oWxLtjiq3gKSCcJ4S8wBnTo/QLtHF66+bhKmVBBYboy3ORmJh3eMpTQqnwE5rQIJT5Ocnqqw5aKTCa+ZPghG9wDklIAm9tmdqhU5NlW2EXOOsxaAOeZbfxOKn+lar6Hrxq+PV/G9Bysq/vzuaF5jjFgkgLYfN6jFHspzu2HJRdl7ifZBJq87j4IBsEXUfCt+C78K6YjVAo/TTqNTxayRQAnfYguExHzVv6duDj578YiauujGFRqZnjU/JxHig6Do6hvt8AcZpmzI5ODsWmX1l80Bt5S4V3ZAU0JpWv7sIwzZt4fRrKYdneRO7SVEwYt44Wmo04EyLAek5N3GxSkkjrV9eMIevU0bSUapzMt0YKxCfz864hS2jQOFNGRalGlW+ysML2W294xyl/vlx0JBno/BpxWAe c8cev1Eg ktQwbAXQnX9HpYKfZF3T47P21bicsqIIqaDX7PdUhQ7gCusOSGwizUi1GxarjJQM2AG71gD21Ytwfhhzek+5lVp90S+viOctDgX2l0HGnOWJjz8KMNadAo46FngIA7z3QOo3O7Lc8vIMRihECIULHO9y5UDJ6AuI X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hello, syzbot found the following issue on: HEAD commit: e8d018dd0257 Linux 6.3-rc3 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13cd8a86c80000 kernel config: https://syzkaller.appspot.com/x/.config?x=cde06fe2cf5765b7 dashboard link: https://syzkaller.appspot.com/bug?extid=6898da502aef574c5f8a 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+6898da502aef574c5f8a@syzkaller.appspotmail.com ====================================================== WARNING: possible circular locking dependency detected 6.3.0-rc3-syzkaller #0 Not tainted ------------------------------------------------------ kswapd0/100 is trying to acquire lock: ffff88801e636b98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: do_writepages+0x1a8/0x640 mm/page-writeback.c:2551 but task is already holding lock: ffffffff8c8e1280 (fs_reclaim){+.+.}-{0:0}, at: set_task_reclaim_state mm/vmscan.c:200 [inline] ffffffff8c8e1280 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0x170/0x1ac0 mm/vmscan.c:7338 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (fs_reclaim){+.+.}-{0:0}: __fs_reclaim_acquire mm/page_alloc.c:4716 [inline] fs_reclaim_acquire+0x11d/0x160 mm/page_alloc.c:4730 might_alloc include/linux/sched/mm.h:271 [inline] slab_pre_alloc_hook mm/slab.h:728 [inline] slab_alloc_node mm/slab.c:3241 [inline] slab_alloc mm/slab.c:3266 [inline] __kmem_cache_alloc_lru mm/slab.c:3443 [inline] kmem_cache_alloc+0x3d/0x3f0 mm/slab.c:3452 kmem_cache_zalloc include/linux/slab.h:710 [inline] ext4_init_io_end+0x27/0x180 fs/ext4/page-io.c:278 ext4_do_writepages+0xbea/0x31e0 fs/ext4/inode.c:2824 ext4_writepages+0x27c/0x5e0 fs/ext4/inode.c:2964 do_writepages+0x1a8/0x640 mm/page-writeback.c:2551 __writeback_single_inode+0x121/0xdc0 fs/fs-writeback.c:1600 writeback_sb_inodes+0x54d/0xe70 fs/fs-writeback.c:1891 __writeback_inodes_wb+0xc6/0x280 fs/fs-writeback.c:1962 wb_writeback+0x7e9/0xa50 fs/fs-writeback.c:2067 wb_check_background_flush fs/fs-writeback.c:2133 [inline] wb_do_writeback fs/fs-writeback.c:2221 [inline] wb_workfn+0x8b0/0xfc0 fs/fs-writeback.c:2248 process_one_work+0x991/0x15c0 kernel/workqueue.c:2390 worker_thread+0x669/0x1090 kernel/workqueue.c:2537 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 -> #0 (&sbi->s_writepages_rwsem){++++}-{0:0}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056 lock_acquire kernel/locking/lockdep.c:5669 [inline] lock_acquire+0x1af/0x520 kernel/locking/lockdep.c:5634 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] ext4_writepages+0x1a9/0x5e0 fs/ext4/inode.c:2963 do_writepages+0x1a8/0x640 mm/page-writeback.c:2551 __writeback_single_inode+0x121/0xdc0 fs/fs-writeback.c:1600 writeback_single_inode+0x2ad/0x590 fs/fs-writeback.c:1721 write_inode_now+0x16e/0x1e0 fs/fs-writeback.c:2757 iput_final fs/inode.c:1735 [inline] iput.part.0+0x408/0x740 fs/inode.c:1774 iput+0x5c/0x80 fs/inode.c:1764 dentry_unlink_inode+0x2b1/0x460 fs/dcache.c:401 __dentry_kill+0x3c0/0x640 fs/dcache.c:607 shrink_dentry_list+0x12c/0x4f0 fs/dcache.c:1201 prune_dcache_sb+0xeb/0x150 fs/dcache.c:1282 super_cache_scan+0x33a/0x590 fs/super.c:104 do_shrink_slab+0x428/0xaa0 mm/vmscan.c:853 shrink_slab_memcg mm/vmscan.c:922 [inline] shrink_slab+0x388/0x660 mm/vmscan.c:1001 shrink_one+0x502/0x810 mm/vmscan.c:5343 shrink_many mm/vmscan.c:5394 [inline] lru_gen_shrink_node mm/vmscan.c:5511 [inline] shrink_node+0x2064/0x35f0 mm/vmscan.c:6459 kswapd_shrink_node mm/vmscan.c:7262 [inline] balance_pgdat+0xa02/0x1ac0 mm/vmscan.c:7452 kswapd+0x677/0xd60 mm/vmscan.c:7712 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(fs_reclaim); lock(&sbi->s_writepages_rwsem); lock(fs_reclaim); lock(&sbi->s_writepages_rwsem); *** DEADLOCK *** 3 locks held by kswapd0/100: #0: ffffffff8c8e1280 (fs_reclaim){+.+.}-{0:0}, at: set_task_reclaim_state mm/vmscan.c:200 [inline] #0: ffffffff8c8e1280 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0x170/0x1ac0 mm/vmscan.c:7338 #1: ffffffff8c8980b0 (shrinker_rwsem){++++}-{3:3}, at: shrink_slab_memcg mm/vmscan.c:895 [inline] #1: ffffffff8c8980b0 (shrinker_rwsem){++++}-{3:3}, at: shrink_slab+0x2a0/0x660 mm/vmscan.c:1001 #2: ffff88801e6300e0 (&type->s_umount_key#50){++++}-{3:3}, at: trylock_super fs/super.c:414 [inline] #2: ffff88801e6300e0 (&type->s_umount_key#50){++++}-{3:3}, at: super_cache_scan+0x70/0x590 fs/super.c:79 stack backtrace: CPU: 1 PID: 100 Comm: kswapd0 Not tainted 6.3.0-rc3-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056 lock_acquire kernel/locking/lockdep.c:5669 [inline] lock_acquire+0x1af/0x520 kernel/locking/lockdep.c:5634 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] ext4_writepages+0x1a9/0x5e0 fs/ext4/inode.c:2963 do_writepages+0x1a8/0x640 mm/page-writeback.c:2551 __writeback_single_inode+0x121/0xdc0 fs/fs-writeback.c:1600 writeback_single_inode+0x2ad/0x590 fs/fs-writeback.c:1721 write_inode_now+0x16e/0x1e0 fs/fs-writeback.c:2757 iput_final fs/inode.c:1735 [inline] iput.part.0+0x408/0x740 fs/inode.c:1774 iput+0x5c/0x80 fs/inode.c:1764 dentry_unlink_inode+0x2b1/0x460 fs/dcache.c:401 __dentry_kill+0x3c0/0x640 fs/dcache.c:607 shrink_dentry_list+0x12c/0x4f0 fs/dcache.c:1201 prune_dcache_sb+0xeb/0x150 fs/dcache.c:1282 super_cache_scan+0x33a/0x590 fs/super.c:104 do_shrink_slab+0x428/0xaa0 mm/vmscan.c:853 shrink_slab_memcg mm/vmscan.c:922 [inline] shrink_slab+0x388/0x660 mm/vmscan.c:1001 shrink_one+0x502/0x810 mm/vmscan.c:5343 shrink_many mm/vmscan.c:5394 [inline] lru_gen_shrink_node mm/vmscan.c:5511 [inline] shrink_node+0x2064/0x35f0 mm/vmscan.c:6459 kswapd_shrink_node mm/vmscan.c:7262 [inline] balance_pgdat+0xa02/0x1ac0 mm/vmscan.c:7452 kswapd+0x677/0xd60 mm/vmscan.c:7712 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 ------------[ cut here ]------------ WARNING: CPU: 1 PID: 100 at fs/ext4/inode.c:5325 ext4_write_inode+0x337/0x590 fs/ext4/inode.c:5325 Modules linked in: CPU: 1 PID: 100 Comm: kswapd0 Not tainted 6.3.0-rc3-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 RIP: 0010:ext4_write_inode+0x337/0x590 fs/ext4/inode.c:5325 Code: b6 04 02 84 c0 74 08 3c 03 0f 8e 3d 02 00 00 8b b5 b0 06 00 00 4c 89 f7 e8 c6 94 12 00 41 89 c4 e9 ed fd ff ff e8 e9 4e 5a ff <0f> 0b 45 31 e4 e9 de fd ff ff e8 da 4e 5a ff 48 89 ef 48 8d 74 24 RSP: 0018:ffffc90000c87360 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 1ffff92000190e6c RCX: 0000000000000000 RDX: ffff8880169700c0 RSI: ffffffff8227b6c7 RDI: 0000000000000005 RBP: ffff8880283852f0 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000000000800 R11: 3e4b5341542f3c20 R12: 0000000000000800 R13: ffffc90000c874e0 R14: dffffc0000000000 R15: ffff888028385318 FS: 0000000000000000(0000) GS:ffff88802ca80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe7eabfe718 CR3: 00000000738f6000 CR4: 0000000000150ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: write_inode fs/fs-writeback.c:1453 [inline] __writeback_single_inode+0x9f8/0xdc0 fs/fs-writeback.c:1665 writeback_single_inode+0x2ad/0x590 fs/fs-writeback.c:1721 write_inode_now+0x16e/0x1e0 fs/fs-writeback.c:2757 iput_final fs/inode.c:1735 [inline] iput.part.0+0x408/0x740 fs/inode.c:1774 iput+0x5c/0x80 fs/inode.c:1764 dentry_unlink_inode+0x2b1/0x460 fs/dcache.c:401 __dentry_kill+0x3c0/0x640 fs/dcache.c:607 shrink_dentry_list+0x12c/0x4f0 fs/dcache.c:1201 prune_dcache_sb+0xeb/0x150 fs/dcache.c:1282 super_cache_scan+0x33a/0x590 fs/super.c:104 do_shrink_slab+0x428/0xaa0 mm/vmscan.c:853 shrink_slab_memcg mm/vmscan.c:922 [inline] shrink_slab+0x388/0x660 mm/vmscan.c:1001 shrink_one+0x502/0x810 mm/vmscan.c:5343 shrink_many mm/vmscan.c:5394 [inline] lru_gen_shrink_node mm/vmscan.c:5511 [inline] shrink_node+0x2064/0x35f0 mm/vmscan.c:6459 kswapd_shrink_node mm/vmscan.c:7262 [inline] balance_pgdat+0xa02/0x1ac0 mm/vmscan.c:7452 kswapd+0x677/0xd60 mm/vmscan.c:7712 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 --- 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@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.