Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2223450imm; Mon, 28 May 2018 04:15:36 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqHftoRDP0NhY4XwWVoEMNFwvb72FJ6AP8UyWpjomvE9qQUFFGZ1aAdzYVJPzG5hzw2ltEA X-Received: by 2002:a17:902:778a:: with SMTP id o10-v6mr13259584pll.214.1527506136310; Mon, 28 May 2018 04:15:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527506136; cv=none; d=google.com; s=arc-20160816; b=YZWjndlbrrpLOLzfiUQPSRfgquvaJCkzfzKmAkioqGItF16j6WIuVVaTdGt0dA+bfV AmnysIjzOus2cHWflXbcD6/RvOEOKC63dmt6qmggKVRx1LEDGnxYcsyoxUaf7NZmbm29 koKzSPYryfA/7D5p3ld5ssMpiLpvoukiJPflrrPI22SpjJ8hXeZ7vVa4uoLd8bOmcnDe mOe0XseQMdCV1zJMBs2MA1f+xAyqcUYg8MLsjTWn5ENsaVooyqo/bKJpa2mqm0eCGYYL zOCZZAMNkPdJ96CChM+8RkOKDjNLCpwuMd+KLhr7n7JExkSTOtaF1UeCSp/026y0+NaR dZEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=/p2zGq0wAx/FXOayQ/CMH1TkFaq8UoWFFDI7mJPILaw=; b=FzOIvpLVQyB2sgvDliJWbAgurMTAq1Ae04ddnnXq7nzlCZ/RFRRQkX9FK9MLX1cSTs WQvM5BDP03eQ1S7ZmDpATEUZKgP6G8c13AQ0g3P+agfWzkftRWRX/afc2FlWmGFXlYA9 vgws/PFBAlesJdgIIP1/1N2aZ7xY77Uo3U39i85jODRtEZsL18YdMOHzLC8cHL92Y4W1 +zNhOnA3/7tMmUF8Ze9AuSh0ZiczdQ1dDu8PY+Y9sYVm3hRjJYmnGFbbSdVCIO6Jxtdi 0yes5dZNJnLDhF1frjYpBpHEQjOo9ID4K4CAq8mdeAWLFgNQYUrMcIp+l/tGeGouFjB1 hK+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Mo3njWnS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j6-v6si30021997pfb.25.2018.05.28.04.15.21; Mon, 28 May 2018 04:15:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Mo3njWnS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1424346AbeE1LOB (ORCPT + 99 others); Mon, 28 May 2018 07:14:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:33164 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423937AbeE1LNu (ORCPT ); Mon, 28 May 2018 07:13:50 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9DEAE20845; Mon, 28 May 2018 11:13:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527506030; bh=S4obAo7Lr7p42s+AaCVDYyAORgAZAxjDiJ5K19JSUoo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Mo3njWnS7i2BG1WPRdqEOpLEg5ymzVBtAxY7DnctBkAEmKsx91EPuvwAd9nfMySgJ feAWgc8LoTeijqSSn/EI1MUlGs0YN9ovSbfGB4JkNmZOHK4PVY0qDrCjhZGdqriOdJ qr6QyeNnKnBAiaMpLHmMShBKJ4tjMY8ot5CnVG6A= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Chao Yu , Jaegeuk Kim , Sasha Levin Subject: [PATCH 4.16 182/272] f2fs: fix to check extent cache in f2fs_drop_extent_tree Date: Mon, 28 May 2018 12:03:35 +0200 Message-Id: <20180528100255.979417715@linuxfoundation.org> X-Mailer: git-send-email 2.17.0 In-Reply-To: <20180528100240.256525891@linuxfoundation.org> References: <20180528100240.256525891@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.16-stable review patch. If anyone has any objections, please let me know. ------------------ From: Chao Yu [ Upstream commit bf617f7a92edc6bb2909db2bfa4576f50b280ee5 ] If noextent_cache mount option is on, we will never initialize extent tree in inode, but still we're going to access it in f2fs_drop_extent_tree, result in kernel panic as below: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 IP: _raw_write_lock+0xc/0x30 Call Trace: ? f2fs_drop_extent_tree+0x41/0x70 [f2fs] f2fs_fallocate+0x5a0/0xdd0 [f2fs] ? common_file_perm+0x47/0xc0 ? apparmor_file_permission+0x1a/0x20 vfs_fallocate+0x15b/0x290 SyS_fallocate+0x44/0x70 do_syscall_64+0x6e/0x160 entry_SYSCALL64_slow_path+0x25/0x25 This patch fixes to check extent cache status before using in f2fs_drop_extent_tree. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- fs/f2fs/extent_cache.c | 3 +++ 1 file changed, 3 insertions(+) --- a/fs/f2fs/extent_cache.c +++ b/fs/f2fs/extent_cache.c @@ -706,6 +706,9 @@ void f2fs_drop_extent_tree(struct inode struct f2fs_sb_info *sbi = F2FS_I_SB(inode); struct extent_tree *et = F2FS_I(inode)->extent_tree; + if (!f2fs_may_extent_tree(inode)) + return; + set_inode_flag(inode, FI_NO_EXTENT); write_lock(&et->lock);