[GIT PULL] Last btrfs fixes for 5.3

[David Sterba]

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(-)