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.5-rc5
Date: Fri,  3 Jan 2020 18:43:16 +0100	[thread overview]
Message-ID: <cover.1578072747.git.dsterba@suse.com> (raw)

Hi,

a few fixes for btrfs:

* blkcg accounting problem with compression that could stall writes

* setting up blkcg bio for compression crashes due to NULL bdev pointer

* fix possible infinite loop in writeback for nocow files (here possible
  means almost impossible, 13 things that need to happen to trigger it)

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit fbd542971aa1e9ec33212afe1d9b4f1106cd85a1:

  btrfs: send: remove WARN_ON for readonly mount (2019-12-13 14:10:46 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.5-rc4-tag

for you to fetch changes up to de7999afedff02c6631feab3ea726a0e8f8c3d40:

  Btrfs: fix infinite loop during nocow writeback due to race (2019-12-30 16:13:20 +0100)

----------------------------------------------------------------
Dennis Zhou (2):
      btrfs: punt all bios created in btrfs_submit_compressed_write()
      btrfs: fix compressed write bio blkcg attribution

Filipe Manana (1):
      Btrfs: fix infinite loop during nocow writeback due to race

 fs/btrfs/compression.c | 7 ++++++-
 fs/btrfs/inode.c       | 6 +++---
 2 files changed, 9 insertions(+), 4 deletions(-)

             reply	other threads:[~2020-01-03 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 17:43 David Sterba [this message]
2020-01-03 20:40 ` [GIT PULL] Btrfs fixes for 5.5-rc5 pr-tracker-bot
2020-01-04 12:32 ` Filipe Manana

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.1578072747.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.