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-rc2
Date: Fri, 26 Jul 2019 18:42:24 +0200	[thread overview]
Message-ID: <cover.1564158940.git.dsterba@suse.com> (raw)

Hi,

please pull two regression fixes:

* hangs caused by a missing barrier in the locking code

* memory leaks of extent_state due to bad handling of a cached pointer

Thanks.

----------------------------------------------------------------
The following changes since commit 373c3b80e459cb57c34381b928588a3794eb5bbd:

  btrfs: don't leak extent_map in btrfs_get_io_geometry() (2019-07-17 17:03:36 +0200)

are available in the Git repository at:

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

for you to fetch changes up to a3b46b86ca76d7f9d487e6a0b594fd1984e0796e:

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

----------------------------------------------------------------
Naohiro Aota (1):
      btrfs: fix extent_state leak in btrfs_lock_and_flush_ordered_range

Nikolay Borisov (1):
      btrfs: Fix deadlock caused by missing memory barrier

 fs/btrfs/locking.c      |  9 ++++++---
 fs/btrfs/ordered-data.c | 11 ++++++-----
 2 files changed, 12 insertions(+), 8 deletions(-)

             reply	other threads:[~2019-07-26 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 16:42 David Sterba [this message]
2019-07-26 18:25 ` [GIT PULL] Btrfs fixes for 5.3-rc2 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-07-22 12:18 David Sterba
2019-07-22 16:40 ` 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.1564158940.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.