public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.11-rc6
Date: Sat, 30 Jan 2021 01:35:38 +0100	[thread overview]
Message-ID: <cover.1611932305.git.dsterba@suse.com> (raw)

Hi,

I'm not sure the first post of this pull request made it through so
sending again.

A few more fixes for a late rc:

- fix lockdep complaint on 32bit arches and also remove an unsafe memory
  use due to device vs filesystem lifetime

- two fixes for free space tree
  - race during log replay and cache rebuild, now more likely to happen
    due to changes in this dev cycle
  - possible free space tree corruption with online conversion during
    initial tree population

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 34d1eb0e599875064955a74712f08ff14c8e3d5f:

  btrfs: don't clear ret in btrfs_start_dirty_block_groups (2021-01-18 16:00:11 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.11-rc5-tag

for you to fetch changes up to 9ad6d91f056b99dbe59a262810cb342519ea8d39:

  btrfs: fix log replay failure due to race with space cache rebuild (2021-01-25 18:44:53 +0100)

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: fix log replay failure due to race with space cache rebuild

Josef Bacik (1):
      btrfs: fix possible free space tree corruption with online conversion

Su Yue (1):
      btrfs: fix lockdep warning due to seqcount_mutex on 32bit arch

 fs/btrfs/block-group.c     | 10 +++++++-
 fs/btrfs/ctree.h           |  3 +++
 fs/btrfs/extent-tree.c     | 61 ++++++++++++++--------------------------------
 fs/btrfs/free-space-tree.c | 10 +++++++-
 fs/btrfs/volumes.c         |  2 +-
 fs/btrfs/volumes.h         | 11 +++++----
 6 files changed, 46 insertions(+), 51 deletions(-)

             reply	other threads:[~2021-01-30  1:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30  0:35 David Sterba [this message]
2021-01-30  0:40 ` [GIT PULL] Btrfs fixes for 5.11-rc6 Linus Torvalds
2021-01-30 20:01 ` 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.1611932305.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