Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/7] btrfs: a fix for fsync and a few improvements to the full fsync path
Date: Thu, 17 Feb 2022 12:12:01 +0000	[thread overview]
Message-ID: <cover.1645098951.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

This fixes a bug (first patch) with preallocated extents beyond eof being
lost after a full fsync and a power failure. The rest is mostly some
improvements to the full fsync code path (less IO, use less memory for
logging checksums, etc), and silence smatch about a possible dereference
of an uninitialized pointer. More details in the changelogs.

Filipe Manana (7):
  btrfs: fix lost prealloc extents beyond eof after full fsync
  btrfs: stop copying old file extents when doing a full fsync
  btrfs: hold on to less memory when logging checksums during full fsync
  btrfs: voluntarily relinquish cpu when doing a full fsync
  btrfs: reset last_reflink_trans after fsyncing inode
  btrfs: fix unexpected error path when reflinking an inline extent
  btrfs: deal with unexpected extent type during reflinking

 fs/btrfs/btrfs_inode.h |  30 +++++
 fs/btrfs/file.c        |   7 +-
 fs/btrfs/inode.c       |  12 +-
 fs/btrfs/reflink.c     |  39 +++---
 fs/btrfs/tree-log.c    | 285 +++++++++++++++++++++++++++--------------
 5 files changed, 254 insertions(+), 119 deletions(-)

-- 
2.33.0


             reply	other threads:[~2022-02-17 12:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 12:12 fdmanana [this message]
2022-02-17 12:12 ` [PATCH 1/7] btrfs: fix lost prealloc extents beyond eof after full fsync fdmanana
2022-02-21 10:11   ` Wang Yugui
2022-02-21 10:41     ` Filipe Manana
2022-02-21 23:51       ` Wang Yugui
2022-02-22 10:29         ` Filipe Manana
2022-02-17 12:12 ` [PATCH 2/7] btrfs: stop copying old file extents when doing a " fdmanana
2022-02-17 12:12 ` [PATCH 3/7] btrfs: hold on to less memory when logging checksums during " fdmanana
2022-02-17 12:12 ` [PATCH 4/7] btrfs: voluntarily relinquish cpu when doing a " fdmanana
2022-02-17 12:12 ` [PATCH 5/7] btrfs: reset last_reflink_trans after fsyncing inode fdmanana
2022-02-17 12:12 ` [PATCH 6/7] btrfs: fix unexpected error path when reflinking an inline extent fdmanana
2022-02-17 12:12 ` [PATCH 7/7] btrfs: deal with unexpected extent type during reflinking fdmanana
2022-02-21 16:15 ` [PATCH 0/7] btrfs: a fix for fsync and a few improvements to the full fsync path 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.1645098951.git.fdmanana@suse.com \
    --to=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox