All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/7] btrfs: fix a bug with truncation and writeback and cleanups
Date: Mon, 13 Oct 2025 13:05:25 +0100	[thread overview]
Message-ID: <cover.1760356778.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

The first patch fixes a bug where we can up persisting a file extent item
that crosses the i_size boundary, making btrfs check complain because it
won't find checksum items beyond the i_size boundary. Details in the change
log. The rest are several cleanups in related code that popped up while
debugging the issue.

Filipe Manana (7):
  btrfs: truncate ordered extent when skipping writeback past i_size
  btrfs: use variable for end offset in extent_writepage_io()
  btrfs: split assertion into two in extent_writepage_io()
  btrfs: add unlikely to unexpected error case in extent_writepages()
  btrfs: consistently round up or down i_size in btrfs_truncate()
  btrfs: avoid multiple i_size rounding in btrfs_truncate()
  btrfs: avoid repeated computations in btrfs_mark_ordered_io_finished()

 fs/btrfs/extent_io.c    | 33 ++++++++++++++++++++++++++-------
 fs/btrfs/inode.c        | 18 ++++++++----------
 fs/btrfs/ordered-data.c | 23 +++++++++++------------
 3 files changed, 45 insertions(+), 29 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-10-13 12:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 12:05 fdmanana [this message]
2025-10-13 12:05 ` [PATCH 1/7] btrfs: truncate ordered extent when skipping writeback past i_size fdmanana
2025-10-13 20:46   ` Qu Wenruo
2025-10-13 12:05 ` [PATCH 2/7] btrfs: use variable for end offset in extent_writepage_io() fdmanana
2025-10-13 20:51   ` Qu Wenruo
2025-10-13 12:05 ` [PATCH 3/7] btrfs: split assertion into two " fdmanana
2025-10-13 20:52   ` Qu Wenruo
2025-10-13 12:05 ` [PATCH 4/7] btrfs: add unlikely to unexpected error case in extent_writepages() fdmanana
2025-10-13 20:52   ` Qu Wenruo
2025-10-13 12:05 ` [PATCH 5/7] btrfs: consistently round up or down i_size in btrfs_truncate() fdmanana
2025-10-13 20:52   ` Qu Wenruo
2025-10-13 12:05 ` [PATCH 6/7] btrfs: avoid multiple i_size rounding " fdmanana
2025-10-13 20:53   ` Qu Wenruo
2025-10-13 12:05 ` [PATCH 7/7] btrfs: avoid repeated computations in btrfs_mark_ordered_io_finished() fdmanana
2025-10-13 20:55   ` Qu Wenruo
2025-10-13 21:01 ` [PATCH 0/7] btrfs: fix a bug with truncation and writeback and cleanups Qu Wenruo
2025-10-13 22:41   ` 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.1760356778.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 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.