linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.6-rc3
Date: Sun, 23 Feb 2020 14:36:29 +0100	[thread overview]
Message-ID: <cover.1582462302.git.dsterba@suse.com> (raw)

Hi,

there are fixes that were found during testing with help of error
injection, plus some other stable material.

There's a fixup to patch added to rc1 causing locking in wrong context
warnings, tests found one more deadlock scenario. The patches are tagged
for stable, two of them now in the queue but we'd like all three
released at the same time.

I'm not happy about fixes to fixes in such a fast succession namely during
rcs, but I hope we found all the fallouts of 28553fa992cb28be. As the
other fixes are not urgent I'm also fine with delaying the pull until
rc4 and coordinating with stable@.

Thanks.

----------------------------------------------------------------
The following changes since commit 52e29e331070cd7d52a64cbf1b0958212a340e28:

  btrfs: don't set path->leave_spinning for truncate (2020-02-17 16:23:06 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.6-rc2-tag

for you to fetch changes up to a5ae50dea9111db63d30d700766dd5509602f7ad:

  Btrfs: fix deadlock during fast fsync when logging prealloc extents beyond eof (2020-02-21 16:21:19 +0100)

----------------------------------------------------------------
Filipe Manana (2):
      Btrfs: fix btrfs_wait_ordered_range() so that it waits for all ordered extents
      Btrfs: fix deadlock during fast fsync when logging prealloc extents beyond eof

Jeff Mahoney (1):
      btrfs: destroy qgroup extent records on transaction abort

Josef Bacik (4):
      btrfs: reset fs_root to NULL on error in open_ctree
      btrfs: do not check delayed items are empty for single transaction cleanup
      btrfs: handle logged extent failure properly
      btrfs: fix bytes_may_use underflow in prealloc error condtition

 fs/btrfs/disk-io.c      |  3 ++-
 fs/btrfs/extent-tree.c  |  2 ++
 fs/btrfs/inode.c        | 26 ++++++++++++++++++--------
 fs/btrfs/ordered-data.c |  7 ++++++-
 fs/btrfs/qgroup.c       | 13 +++++++++++++
 fs/btrfs/qgroup.h       |  1 +
 fs/btrfs/transaction.c  |  2 ++
 7 files changed, 44 insertions(+), 10 deletions(-)

             reply	other threads:[~2020-02-23 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 13:36 David Sterba [this message]
2020-02-23 17:50 ` [GIT PULL] Btrfs fixes for 5.6-rc3 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1582462302.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).