Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3411445pxf; Mon, 29 Mar 2021 01:14:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxdUiWcxGCzq7cDFPvY3ZSsxdr811LX1KXIMr4wRb9xhIId7f8B9OYQMigWE58z3xybKEH0 X-Received: by 2002:a05:6402:26d3:: with SMTP id x19mr15454366edd.349.1617005647516; Mon, 29 Mar 2021 01:14:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617005647; cv=none; d=google.com; s=arc-20160816; b=ZZ5RVzSFGv/GsuzhwELhkjbMgioSKhq+1dNNxgF/xjr51DolKjDdnLb2PLfS0mY24Q SO+OXoLy6ltueKuZvvZAtqdi6V17MaQDEpODs2Bcp3HlG6fzT5yhzc+/EXdiB60nnFAv 3pzn14RozCglMwCdFFhK2GdVM3HPiJBJ1Rj9NE8CDBdNwpqfu9kE+2bDYx5eoX9Xwneh ecyabqrU9YLyKWFNAZ/kepF+z0gYu0nDuceD8g44VbloEWsMLGx6KIPpZ314yyTAmfJD E36k7ecZv6p+e6cEUre8Hl+zAYjUyeKZSCVejmDAtcIVzbmxjHO6+eLEiDPQVLi+uvpo 9Phg== 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=omDo0MeY5RdZXClTZFLln8jV+DKgeXl00nJfGbhAGjc=; b=mdhGNspzHibtLIdWlKlksfoak+2p0HVbU+N9Y2wOyV3IcwIISxvJuf2B4K34Zr6wa6 Pr6unkgvhU/P6ucRdzDeqaszpRtbpCCQZHD9q5YdsNSQZ/ibXNX9vADACcUd4d+w6K0I oq+hoRqHxODZOFS28maAQJ+Z4WsuSSDjTqJxW+hcVy5R6Cgrm3KKjMvsxVzD8NUFR9/N jnC6mer/WjbjiHL0nxUMyrCUPt11GSG8IViLnkYw9ilJvVvimoao7kgsEFNwYtymsvNx 38FgI//+FEcEHUZ01s7iWDUG+pYqj9NweZqfW3ePhDwyETQeXWoP5KeGKVcgUc5KeGGh oHXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="Quix/f8T"; 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 l3si13587655ejd.203.2021.03.29.01.13.45; Mon, 29 Mar 2021 01:14:07 -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="Quix/f8T"; 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 S232685AbhC2ILb (ORCPT + 99 others); Mon, 29 Mar 2021 04:11:31 -0400 Received: from mail.kernel.org ([198.145.29.99]:49074 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232345AbhC2IGe (ORCPT ); Mon, 29 Mar 2021 04:06:34 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 26BEC61932; Mon, 29 Mar 2021 08:06:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1617005193; bh=+CSIDUoEPFTCArLXmqlLFa5UMXiV+bn7RaHR6vdETL0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Quix/f8TgW0ypSoBVXnlzSHUq00lCLyPXiVt0ScsoH9cgNG1YJHdLyDHxrKla+sFZ K93XbBp/BpzB0iFiJz88uRYQWo4+47GxJLfj6cnxEdPF9yEGBOWXorD3fR6yIz6Rsz 5oWg3efsftXnKU5g5bxBl5CZlzBfzckz94Dkpkq0= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Jan Kara , Theodore Tso Subject: [PATCH 4.14 58/59] ext4: add reclaim checks to xattr code Date: Mon, 29 Mar 2021 09:58:38 +0200 Message-Id: <20210329075610.780311481@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210329075608.898173317@linuxfoundation.org> References: <20210329075608.898173317@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 @@ -1479,6 +1479,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); @@ -2345,6 +2348,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);