All of lore.kernel.org
 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.9-rc8
Date: Fri,  2 Oct 2020 17:30:36 +0200	[thread overview]
Message-ID: <cover.1601650060.git.dsterba@suse.com> (raw)

Hi,

two more fixes. One is for a lockdep warning/lockup (also caught by
syzbot), that one has been seen in practice.  Regarding the other syzbot
reports mentioned last time, they don't seem to be urgent and reliably
reproducible so they'll be fixed later.

The second fix is for a potential corruption when device replace
finishes and the in-memory state of trim is not copied to the new
device.

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit b5ddcffa37778244d5e786fe32f778edf2bfc93e:

  btrfs: fix put of uninitialized kobject after seed device delete (2020-09-22 15:57:52 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.9-rc7-tag

for you to fetch changes up to 4c8f353272dd1262013873990c0fafd0e3c8f274:

  btrfs: fix filesystem corruption after a device replace (2020-09-30 19:40:51 +0200)

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: fix filesystem corruption after a device replace

Josef Bacik (2):
      btrfs: move btrfs_scratch_superblocks into btrfs_dev_replace_finishing
      btrfs: move btrfs_rm_dev_replace_free_srcdev outside of all locks

 fs/btrfs/dev-replace.c | 46 ++++++++++++++++++++++++++++++++++++++++++++--
 fs/btrfs/volumes.c     | 13 +++++--------
 fs/btrfs/volumes.h     |  3 +++
 3 files changed, 52 insertions(+), 10 deletions(-)

             reply	other threads:[~2020-10-02 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 15:30 David Sterba [this message]
2020-10-02 17:15 ` [GIT PULL] Btrfs fixes for 5.9-rc8 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.1601650060.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.