public inbox for linux-btrfs@vger.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 updates for 6.7-rc2
Date: Mon, 13 Nov 2023 17:22:47 +0100	[thread overview]
Message-ID: <cover.1699891630.git.dsterba@suse.com> (raw)

Hi,

please pull the following fixes that accumulated in the past weeks.

- fix potential overflow in returned value from SEARCH_TREE_V2 ioctl on
  32bit architecture

- zoned mode fixes

  - drop unnecessary write pointer check for RAID0/RAID1/RAID10
    profiles, now it works because of raid-stripe-tree

  - wait for finishing the zone when direct IO needs a new allocation

- simple quota fixes

  - pass correct owning root pointer when cleaning up an aborted
    transaction

  - fix leaking some structures when processing delayed refs

  - change key type number of BTRFS_EXTENT_OWNER_REF_KEY, reorder it
    before inline refs that are supposed to be sorted, keeping the
    original number would complicate a lot of things; this change needs
    an updated version of btrfs-progs to work and filesystems need to be
    recreated

- fix error pointer dereference after failure to allocate fs devices

- fix race between accounting qgroup extents and removing a qgroup

----------------------------------------------------------------
The following changes since commit c6e8f898f56fae2cb5bc4396bec480f23cd8b066:

  btrfs: open code timespec64 in struct btrfs_inode (2023-10-12 16:44:19 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.7-rc1-tag

for you to fetch changes up to d3933152442b7f94419e9ea71835d71b620baf0e:

  btrfs: make OWNER_REF_KEY type value smallest among inline refs (2023-11-09 14:02:12 +0100)

----------------------------------------------------------------
Boris Burkov (1):
      btrfs: make OWNER_REF_KEY type value smallest among inline refs

Dan Carpenter (1):
      btrfs: directly return 0 on no error code in btrfs_insert_raid_extent()

Filipe Manana (4):
      btrfs: use u64 for buffer sizes in the tree search ioctls
      btrfs: fix error pointer dereference after failure to allocate fs devices
      btrfs: fix race between accounting qgroup extents and removing a qgroup
      btrfs: fix qgroup record leaks when using simple quotas

Josef Bacik (1):
      btrfs: get correct owning_root when dropping snapshot

Naohiro Aota (2):
      btrfs: zoned: drop no longer valid write pointer check
      btrfs: zoned: wait for data BG to be finished on direct IO allocation

Qu Wenruo (1):
      btrfs: make found_logical_ret parameter mandatory for function queue_scrub_stripe()

 fs/btrfs/ctree.c                |  2 +-
 fs/btrfs/delayed-ref.c          |  4 ++--
 fs/btrfs/extent-tree.c          | 25 +++++++++++++++++--------
 fs/btrfs/extent-tree.h          |  3 ++-
 fs/btrfs/inode.c                |  7 +++++++
 fs/btrfs/ioctl.c                | 10 +++++-----
 fs/btrfs/qgroup.c               | 10 ++++++++--
 fs/btrfs/raid-stripe-tree.c     |  2 +-
 fs/btrfs/scrub.c                | 10 +++++++---
 fs/btrfs/volumes.c              |  6 +++---
 fs/btrfs/zoned.c                |  7 -------
 include/uapi/linux/btrfs_tree.h | 24 ++++++++++++++++--------
 12 files changed, 69 insertions(+), 41 deletions(-)

             reply	other threads:[~2023-11-13 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 16:22 David Sterba [this message]
2023-11-13 17:16 ` [GIT PULL] Btrfs updates for 6.7-rc2 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.1699891630.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