Linux Btrfs filesystem development
 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 6.5-rc7
Date: Sat, 19 Aug 2023 17:35:53 +0200	[thread overview]
Message-ID: <cover.1692453407.git.dsterba@suse.com> (raw)

Hi,

a few more short fixes sent recently but still seem important enough for
a late rc. Please pull, thanks.

* fix infinite loop in readdir(), could happen in a big directory when
  files get renamed during enumeration

* fix extent map handling of skipped pinned ranges

* fix a corner case when handling ordered extent length

* fix a potential crash when balance cancel races with pause

* verify correct uuid when starting scrub or device replace

----------------------------------------------------------------
The following changes since commit 92fb94b69c6accf1e49fff699640fa0ce03dc910:

  btrfs: set cache_block_group_error if we find an error (2023-08-10 17:16:45 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.5-rc6-tag

for you to fetch changes up to c962098ca4af146f2625ed64399926a098752c9c:

  btrfs: fix incorrect splitting in btrfs_drop_extent_map_range (2023-08-18 14:38:10 +0200)

----------------------------------------------------------------
Anand Jain (1):
      btrfs: fix replace/scrub failure with metadata_uuid

Chris Mason (1):
      btrfs: only subtract from len_to_oe_boundary when it is tracking an extent

Filipe Manana (1):
      btrfs: fix infinite directory reads

Josef Bacik (1):
      btrfs: fix incorrect splitting in btrfs_drop_extent_map_range

xiaoshoukui (1):
      btrfs: fix BUG_ON condition in btrfs_cancel_balance

 fs/btrfs/ctree.h         |   1 +
 fs/btrfs/delayed-inode.c |   5 +-
 fs/btrfs/delayed-inode.h |   1 +
 fs/btrfs/extent_io.c     |  25 ++++++++-
 fs/btrfs/extent_map.c    |   6 +--
 fs/btrfs/inode.c         | 131 ++++++++++++++++++++++++++++-------------------
 fs/btrfs/scrub.c         |   3 +-
 fs/btrfs/volumes.c       |   3 +-
 8 files changed, 113 insertions(+), 62 deletions(-)

             reply	other threads:[~2023-08-19 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-19 15:35 David Sterba [this message]
2023-08-19 16:01 ` [GIT PULL] Btrfs fixes for 6.5-rc7 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.1692453407.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox