Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3491417pxf; Mon, 29 Mar 2021 03:52:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwRLFTrWLOXjxkcqGs+TSFarCkUg+WDPEItx0ly1MP2l70ZOpF23VHT3GuKafQxsK9F/Igc X-Received: by 2002:a17:907:778d:: with SMTP id ky13mr27934468ejc.291.1617015167610; Mon, 29 Mar 2021 03:52:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617015167; cv=none; d=google.com; s=arc-20160816; b=Q/+Yj2t8KcPM7RKDYlbsFrEfMOO43XNVecqbvtRcav2HvICkW84jW//vQiKczsUuWi q5LW2I9XcxSuUycm6HsBvuDvA+8IrsKlOo8BOu8znI014JxvTk5ZKM4Z3sP0FNexNfNq PwLNlS2gjY1HvfivoE+DOyBOk+6VAzGX50/byRnVS9zlnlpGTcAs5jWsuerVcZOh8IZb hXfTRI8FZ7BcugK7zkvspg09IweLYeHCiDugdcLNRASCovgCBkqAdW53mDivZvd83Hdw RQZ163EUNrbFsnD57XtxB0Lf8N4CIfLd6iEajw2mXHSHzX4sFLCcmpnPgxT1T1XqoQWm wIjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=txLxNHOiKY90u7Rb4PyGw/yiCgMddPZWTldv7fdNHdY=; b=iAVfOC61xk0K+9L57ZLsxv7Dhy9zP4EekmViydL1QKluou3+aZW+rVKFDSPYRjM8uO NXRM2oHyVleSfHrJ2oFrhEeNLUSBvmhuslZbDhF4YheRKQqnaNC0vsxHutpaqRoEcitY bB1iwngOtCJSu8HIQ6CH+4/2kxHD0rBCrQ2wdDZY4aHDEt6THEfKuwrO1a8dd5hOrMZ4 kb4PWhf1e/u7EMseBAQN/XXrQk6XJblE/ZNiLjmiy2PcCXKdmZoi/BQUTpQmHJXmiAG1 23ili2zfy+dURE0MA4xl61C6q6dZlj9BxvwF5iuw2rf66fZHikX7D1cbJWaqkGdCXl3F tvMQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=A+RPZSlp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z4si13350283edc.579.2021.03.29.03.52.25; Mon, 29 Mar 2021 03:52:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=A+RPZSlp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234716AbhC2IlI (ORCPT + 99 others); Mon, 29 Mar 2021 04:41:08 -0400 Received: from mail.kernel.org ([198.145.29.99]:57914 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232754AbhC2IRB (ORCPT ); Mon, 29 Mar 2021 04:17:01 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id C37BC619C2; Mon, 29 Mar 2021 08:16:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1617005788; bh=jVpHT3HT7JE/3luCOdYVQh/Sr8a+M6O3OHX17rPfMoM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=A+RPZSlpvEYFEBvyo9G3cUIXY/+X/h67weXBg8jzgh9et3SCJh6IsHhxwlMvax6ys vVZL779H8AiD1GxDZObEzfspSVut3l10Yn5boGohp1O1iNYfgNgJWyJ1pCpvRn5vZN Woah6UnmNnMqXTKwN3le8ejm9ceSSCRV1Ou9olsI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Jan Kara , Theodore Tso Subject: [PATCH 5.4 110/111] ext4: add reclaim checks to xattr code Date: Mon, 29 Mar 2021 09:58:58 +0200 Message-Id: <20210329075618.863448796@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210329075615.186199980@linuxfoundation.org> References: <20210329075615.186199980@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jan Kara commit 163f0ec1df33cf468509ff38cbcbb5eb0d7fac60 upstream. Syzbot is reporting that ext4 can enter fs reclaim from kvmalloc() while the transaction is started like: fs_reclaim_acquire+0x117/0x150 mm/page_alloc.c:4340 might_alloc include/linux/sched/mm.h:193 [inline] slab_pre_alloc_hook mm/slab.h:493 [inline] slab_alloc_node mm/slub.c:2817 [inline] __kmalloc_node+0x5f/0x430 mm/slub.c:4015 kmalloc_node include/linux/slab.h:575 [inline] kvmalloc_node+0x61/0xf0 mm/util.c:587 kvmalloc include/linux/mm.h:781 [inline] ext4_xattr_inode_cache_find fs/ext4/xattr.c:1465 [inline] ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1508 [inline] ext4_xattr_set_entry+0x1ce6/0x3780 fs/ext4/xattr.c:1649 ext4_xattr_ibody_set+0x78/0x2b0 fs/ext4/xattr.c:2224 ext4_xattr_set_handle+0x8f4/0x13e0 fs/ext4/xattr.c:2380 ext4_xattr_set+0x13a/0x340 fs/ext4/xattr.c:2493 This should be impossible since transaction start sets PF_MEMALLOC_NOFS. Add some assertions to the code to catch if something isn't working as expected early. Link: https://lore.kernel.org/linux-ext4/000000000000563a0205bafb7970@google.com/ Signed-off-by: Jan Kara Link: https://lore.kernel.org/r/20210222171626.21884-1-jack@suse.cz Signed-off-by: Theodore Ts'o Signed-off-by: Greg Kroah-Hartman --- fs/ext4/xattr.c | 4 ++++ 1 file changed, 4 insertions(+) --- a/fs/ext4/xattr.c +++ b/fs/ext4/xattr.c @@ -1476,6 +1476,9 @@ ext4_xattr_inode_cache_find(struct inode if (!ce) return NULL; + WARN_ON_ONCE(ext4_handle_valid(journal_current_handle()) && + !(current->flags & PF_MEMALLOC_NOFS)); + ea_data = ext4_kvmalloc(value_len, GFP_NOFS); if (!ea_data) { mb_cache_entry_put(ea_inode_cache, ce); @@ -2342,6 +2345,7 @@ ext4_xattr_set_handle(handle_t *handle, error = -ENOSPC; goto cleanup; } + WARN_ON_ONCE(!(current->flags & PF_MEMALLOC_NOFS)); } error = ext4_reserve_inode_write(handle, inode, &is.iloc);