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>,
	clm@fb.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.3-rc3
Date: Fri,  2 Aug 2019 18:50:19 +0200	[thread overview]
Message-ID: <cover.1564757308.git.dsterba@suse.com> (raw)

Hi,

please pull the branch with the following fixes:

* tiny race window during 2 transactions aborting at the same time can
  accidentally lead to a commit

* regression fix, possible deadlock during fiemap

* fix for an old bug when incremental send can fail on a file that has
  been deduplicated in a special way

Thanks.

----------------------------------------------------------------
The following changes since commit a3b46b86ca76d7f9d487e6a0b594fd1984e0796e:

  btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range (2019-07-26 12:21:22 +0200)

are available in the Git repository at:

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

for you to fetch changes up to a6d155d2e363f26290ffd50591169cb96c2a609e:

  Btrfs: fix deadlock between fiemap and transaction commits (2019-07-30 18:25:12 +0200)

----------------------------------------------------------------
Filipe Manana (3):
      Btrfs: fix incremental send failure after deduplication
      Btrfs: fix race leading to fs corruption after transaction abort
      Btrfs: fix deadlock between fiemap and transaction commits

 fs/btrfs/backref.c     |  2 +-
 fs/btrfs/send.c        | 77 ++++++++++----------------------------------------
 fs/btrfs/transaction.c | 32 ++++++++++++++++++---
 fs/btrfs/transaction.h |  3 ++
 4 files changed, 47 insertions(+), 67 deletions(-)

             reply	other threads:[~2019-08-02 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 16:50 David Sterba [this message]
2019-08-02 22:10 ` [GIT PULL] Btrfs fixes for 5.3-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.1564757308.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=clm@fb.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.