Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2258163imm; Mon, 28 May 2018 04:57:08 -0700 (PDT) X-Google-Smtp-Source: AB8JxZr5VrHtbS6lOqBWvA1OJxmvEL2uMqbH2dv4QfZXlTZ33qxW0aMW+Sy8pyrnpcJUn9sm09Cw X-Received: by 2002:a63:770c:: with SMTP id s12-v6mr10174822pgc.17.1527508628119; Mon, 28 May 2018 04:57:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527508628; cv=none; d=google.com; s=arc-20160816; b=WfVr5BtSidH1jn4VGMwOpZ3aV6Z5lh9ea5HXqMmEJcY33Cr5iiXJQgcLkUicJ6FMlo TIFUV0EI86F9/rmPWVPJm7mnpkbA79/mLgnMQz9RYED3R+WaOVTVKn7+uho4IjrTFkmB FtW7wnS0kbCXAtpIVOWstYWbu5OymF7VBuVayElrnavtsCIqkt6ynDVqVLbLMXvkKT2b RM9ps3FFThO2/a49gb+qiVlmpMxNvR6TZDsie+Z968y3SpoSTjMLnoaJfP+K2jBvI3o/ rxbUCosrSQ7quSw5d68/RefIddz+bR15YxqkWrdsYFMtKSpX8ifNifXMPpseL0/x6h9C Modw== 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=qtOo/kEIFdsCQzhWFAKY+rTy7BSxEnNQ/kUsmj16l+c=; b=kCgWJtd0O3i5c7dkx9cXzW7WeJdGZVz26xIC/NoT3sNoLhzmWZkHbVWLasvoGnq96P WTkES9CSfqIJVu5ztX/DVByd8nygCmYxKNPQk2wry64/SyzGN6DZkO14cf3TIxa9WyeB 4ZMKGPkj3detQUbGWhANCCSNc8M+IW5f2kap740AOsBGQqCEuEgYLoTxDharfMncqKI2 3bBCqO060V7DkcQYoiCIxdYVX/aVTyiKgA6aQiwvFzMKUWix26vtdm5yuH3JCdDWuiJE hQoZY3XvwVlWykGrqb0DnRHcQUp98aTnpl8USs4tIOnbjMW8zAC56p3YI42WAvyPSGzy ppWg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=oyUAvmf/; 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 3-v6si29386318plm.428.2018.05.28.04.56.53; Mon, 28 May 2018 04:57:08 -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=oyUAvmf/; 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 S1423585AbeE1LIY (ORCPT + 99 others); Mon, 28 May 2018 07:08:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:55290 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423522AbeE1LIC (ORCPT ); Mon, 28 May 2018 07:08:02 -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 B03D2206B7; Mon, 28 May 2018 11:08:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527505682; bh=LDFkUh6qyzzEFR7rdgdtHxOhUnFwbwsOYSX1Jr6p4L0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=oyUAvmf/veapDKkV411qosYlI5+fm51OCTi8aZ4228QjY7yZWjBOyb1sW8CWbBFi5 JQI+/mwwSxic8Ogwv8oxnscstJS4e6D2bQisODzFlDdvyKjgUvSZUdWIXr3t4Jnho2 +ob1Aa7GCrk6EQRTT1mBPd9rHQ9akHM18ukN2PFU= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Filipe Manana , David Sterba , Sasha Levin Subject: [PATCH 4.16 091/272] Btrfs: fix copy_items() return value when logging an inode Date: Mon, 28 May 2018 12:02:04 +0200 Message-Id: <20180528100248.811058484@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: Filipe Manana [ Upstream commit 8434ec46c6e3232cebc25a910363b29f5c617820 ] When logging an inode, at tree-log.c:copy_items(), if we call btrfs_next_leaf() at the loop which checks for the need to log holes, we need to make sure copy_items() returns the value 1 to its caller and not 0 (on success). This is because the path the caller passed was released and is now different from what is was before, and the caller expects a return value of 0 to mean both success and that the path has not changed, while a return value of 1 means both success and signals the caller that it can not reuse the path, it has to perform another tree search. Even though this is a case that should not be triggered on normal circumstances or very rare at least, its consequences can be very unpredictable (especially when replaying a log tree). Fixes: 16e7549f045d ("Btrfs: incompatible format change to remove hole extents") Signed-off-by: Filipe Manana Signed-off-by: David Sterba Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- fs/btrfs/tree-log.c | 1 + 1 file changed, 1 insertion(+) --- a/fs/btrfs/tree-log.c +++ b/fs/btrfs/tree-log.c @@ -4005,6 +4005,7 @@ fill_holes: ASSERT(ret == 0); src = src_path->nodes[0]; i = 0; + need_find_last_extent = true; } btrfs_item_key_to_cpu(src, &key, i);