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.13-rc5
Date: Thu,  3 Jun 2021 16:50:15 +0200	[thread overview]
Message-ID: <cover.1622728563.git.dsterba@suse.com> (raw)

Hi,

this is a batch from last week, I wanted to give it more testing because
last pull request introduced a bug, interacting zoned and subpage
features. Otherwise there are error handling improvements and bug
fixes. The last commit is from today, adding IRC link to maintainers
file.

Please pull, thanks.

- error handling improvements, caught by error injection
  - handle errors during checksum deletion
  - set error on mapping when ordered extent io cannot be finished
  - inode link count fixup in tree-log
  - missing return value checks for inode updates in tree-log
  - abort transaction in rename exchange if adding second reference fails

- fixes
  - fix fsync failure after writes to prealloc extents
  - fix deadlock when cloning inline extents and low on available space
  - fix compressed writes that cross stripe boundary

----------------------------------------------------------------
The following changes since commit 764c7c9a464b68f7c6a5a9ec0b923176a05e8e8f:

  btrfs: zoned: fix parallel compressed writes (2021-05-20 15:51:07 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 503d1acb01826b42e5afb496dfcc32751bec9478:

  MAINTAINERS: add btrfs IRC link (2021-06-03 15:40:38 +0200)

----------------------------------------------------------------
David Sterba (1):
      MAINTAINERS: add btrfs IRC link

Filipe Manana (2):
      btrfs: fix fsync failure and transaction abort after writes to prealloc extents
      btrfs: fix deadlock when cloning inline extents and low on available space

Josef Bacik (6):
      btrfs: fix error handling in btrfs_del_csums
      btrfs: return errors from btrfs_del_csums in cleanup_ref_head
      btrfs: mark ordered extent and inode with error if we fail to finish
      btrfs: fixup error handling in fixup_inode_link_counts
      btrfs: check error value from btrfs_update_inode in tree log
      btrfs: abort in rename_exchange if we fail to insert the second ref

Qu Wenruo (1):
      btrfs: fix compressed writes that cross stripe boundary

 MAINTAINERS            |   1 +
 fs/btrfs/compression.c |  17 +++++---
 fs/btrfs/extent-tree.c |   2 +-
 fs/btrfs/file-item.c   | 108 ++++++++++++++++++++++++++++++++++++-------------
 fs/btrfs/inode.c       |  19 ++++++++-
 fs/btrfs/reflink.c     |  38 +++++++++--------
 fs/btrfs/tree-log.c    |  21 ++++++----
 7 files changed, 148 insertions(+), 58 deletions(-)

             reply	other threads:[~2021-06-03 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 14:50 David Sterba [this message]
2021-06-03 19:09 ` [GIT PULL] Btrfs fixes for 5.13-rc5 pr-tracker-bot
2021-06-04  1:17 ` Naohiro Aota
2021-06-04 11:10   ` David Sterba

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