Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5167998imu; Tue, 15 Jan 2019 12:26:48 -0800 (PST) X-Google-Smtp-Source: ALg8bN5Ea5jhloOPk61Y43tZeVDL5s+wqQoiHlGAvdM3d4h4r9UCDJ2l7tbLLBivffk+rMFeigSU X-Received: by 2002:a63:cf02:: with SMTP id j2mr5501825pgg.113.1547584008438; Tue, 15 Jan 2019 12:26:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547584008; cv=none; d=google.com; s=arc-20160816; b=DuASENPNkLPmZa2CnHDeTZrbZbQRa3Iju+tHV2ynaw506ujptrxF+TDzVzgkDNHv6r hZxcgOYiBReIOv2W838RIl5B1Kh+iwSk99pA5Yd2TrC3XpfY5CVvSv//vzGn9DlTJUZY qjR73eW5denUOenYFkB7T9rs++yRVoVJ1U6XuUaTfLc6gbumQhbPbYewmpUordjKph6c WJWpCAc5RhmKpOJwk2x7IHKlBDGRHAQosAwM6cdKVmmeSwkeahQGXVM1kmhSlsklYIRj oKqWQh099vXOjhSIYBZn0nx6Z2hOgb8IM0nj7CU/IA3lORqW6xTgUqBxA/IuI23/00jk pPXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=fwd1TTfyAS2/b4HC2FZy9Z1XlkibhiOxKn36isB14tw=; b=anZG/HtL34V2cDz5EeoLKsRrSZXrByp/B+54nPN7pztuNTLI2JoprqxdOWVMM4oqFP tIbIHyRY8GeIAOodT+yugRsl6vijT9+J5SnvKa8MeK+vr6NszHSzHktUFRPF4JXnf7sU Y2y/fBKaZUDLJ68X7BF0FG7cRdR5uyY9dUpEkv7jrQoFZjC+on/Ef4cOx9wA+ZgKi6Ec IkaE/38288dNK+Tr3Eq6LWYKT+aivklBVUzx6+jNi/cT8/2VS1yOrWuSqRV85YGCFMGs vSzI65+CQGYsUNU3BAwZoDpoj0qa+xaxLwuORK9fEOHZT77yTv6qHxB/rO17yKV15GM+ n6Qg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=IvVIYYMT; 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 q5si4194675pgb.245.2019.01.15.12.26.29; Tue, 15 Jan 2019 12:26:48 -0800 (PST) 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=IvVIYYMT; 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 S1732365AbfAOQjb (ORCPT + 99 others); Tue, 15 Jan 2019 11:39:31 -0500 Received: from mail.kernel.org ([198.145.29.99]:55570 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732346AbfAOQj0 (ORCPT ); Tue, 15 Jan 2019 11:39:26 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (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 EC0A82054F; Tue, 15 Jan 2019 16:39:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547570365; bh=sCXDiBO19Cef8htAnAM9I2796qaLC3B87m2G038gy2g=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=IvVIYYMTWp2lPfGMcg+AUdgfsLGA5zA3W08KFlqHLOPGLL4FH72VddFJ0ZxHBWMYP RpDKW4KCPEIVzh6TerrB2m1xFJ/rvZzgAo+4vbUnCKlsnuezjAj0LR2FFzOu6q3vXj pCtIRM0+EJwYyTyIpNyxaCk50Naer2R/20sVymv8= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Theodore Tso , stable@kernel.org Subject: [PATCH 4.9 14/16] ext4: fix a potential fiemap/page fault deadlock w/ inline_data Date: Tue, 15 Jan 2019 17:35:57 +0100 Message-Id: <20190115154849.886322430@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190115154848.164648613@linuxfoundation.org> References: <20190115154848.164648613@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Theodore Ts'o commit 2b08b1f12cd664dc7d5c84ead9ff25ae97ad5491 upstream. The ext4_inline_data_fiemap() function calls fiemap_fill_next_extent() while still holding the xattr semaphore. This is not necessary and it triggers a circular lockdep warning. This is because fiemap_fill_next_extent() could trigger a page fault when it writes into page which triggers a page fault. If that page is mmaped from the inline file in question, this could very well result in a deadlock. This problem can be reproduced using generic/519 with a file system configuration which has the inline_data feature enabled. Signed-off-by: Theodore Ts'o Cc: stable@kernel.org Signed-off-by: Greg Kroah-Hartman --- fs/ext4/inline.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) --- a/fs/ext4/inline.c +++ b/fs/ext4/inline.c @@ -1859,12 +1859,12 @@ int ext4_inline_data_fiemap(struct inode physical += (char *)ext4_raw_inode(&iloc) - iloc.bh->b_data; physical += offsetof(struct ext4_inode, i_block); - if (physical) - error = fiemap_fill_next_extent(fieinfo, start, physical, - inline_len, flags); brelse(iloc.bh); out: up_read(&EXT4_I(inode)->xattr_sem); + if (physical) + error = fiemap_fill_next_extent(fieinfo, start, physical, + inline_len, flags); return (error < 0 ? error : 0); }