From patchwork Thu Sep 12 17:37:26 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: David Sterba X-Patchwork-Id: 11143541 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 87E0D1599 for ; Thu, 12 Sep 2019 17:37:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7138120830 for ; Thu, 12 Sep 2019 17:37:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387758AbfILRhJ (ORCPT ); Thu, 12 Sep 2019 13:37:09 -0400 Received: from mx2.suse.de ([195.135.220.15]:33424 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2387431AbfILRhJ (ORCPT ); Thu, 12 Sep 2019 13:37:09 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 5DC0DAEF8; Thu, 12 Sep 2019 17:37:07 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 3B506DA835; Thu, 12 Sep 2019 19:37:28 +0200 (CEST) From: David Sterba To: torvalds@linux-foundation.org Cc: David Sterba , clm@fb.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [GIT PULL] Last btrfs fixes for 5.3 Date: Thu, 12 Sep 2019 19:37:26 +0200 Message-Id: X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org Hi, there are two fixes, one of them urgent fixing a bug introduced in 5.2 and reported by many users. It took time to identify the root cause, catching the 5.3 release is higly desired also to push the fix to 5.2 stable tree. The bug is a mess up of return values after adding proper error handling and honestly the kind of bug that can cause sleeping disorders until it's caught. My appologies to everybody who was affected. Summary of what could happen: 1) either a hang when committing a transaction, if this happens there's no risk of corruption, still the hang is very inconvenient and can't be resolved without a reboot 2) writeback for some btree nodes may never be started and we end up committing a transaction without noticing that, this is really serious and that will lead to the "parent transid verify failed" messages Please pull, thanks. ---------------------------------------------------------------- The following changes since commit 07301df7d2fc220d3de5f7ad804dcb941400cb00: btrfs: trim: Check the range passed into to prevent overflow (2019-08-07 16:42:39 +0200) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.3-rc8-tag for you to fetch changes up to 18dfa7117a3f379862dcd3f67cadd678013bb9dd: Btrfs: fix unwritten extent buffers and hangs on future writeback attempts (2019-09-12 13:37:25 +0200) ---------------------------------------------------------------- Filipe Manana (2): Btrfs: fix assertion failure during fsync and use of stale transaction Btrfs: fix unwritten extent buffers and hangs on future writeback attempts fs/btrfs/extent_io.c | 35 ++++++++++++++++++++++++++--------- fs/btrfs/tree-log.c | 16 ++++++++-------- 2 files changed, 34 insertions(+), 17 deletions(-)