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 7.1-rc5
Date: Sat, 23 May 2026 17:04:09 +0200	[thread overview]
Message-ID: <cover.1779547014.git.dsterba@suse.com> (raw)

Hi,

please pull a batch of fixes to simple quotas and one fix to inode size
handling. Thanks.

- simple quota fixes:
  - add conditional rescheduling point not dependent on the lock during
    inode iterations to avoid delays with PREEMPT_NONE enabled
  - fix subvolume deletion so it does not break the squota invariants
  - properly handle enabling squota, tracking extents in the initial
    transaction
  - catch and warn about underflows, clamp to zero to avoid further
    problems

- fix handling of preallocated extents beyond i_size when not using the
  no-holes feature

----------------------------------------------------------------
The following changes since commit c562ba61fc5e11798720acc1b172862158f1fa0b:

  btrfs: fix incorrect i_size after remount caused by KEEP_SIZE prealloc gap (2026-05-08 00:32:08 +0200)

are available in the Git repository at:

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

for you to fetch changes up to f13342e15deafb7538a7a8577ed5f4c33c56f64e:

  btrfs: swallow btrfs_record_squota_delta() ENOENT (2026-05-16 03:08:40 +0200)

----------------------------------------------------------------
Boris Burkov (5):
      btrfs: always drop root->inodes lock before cond_resched()
      btrfs: check for subvolume before deleting squota qgroup
      btrfs: fix squota accounting during enable generation
      btrfs: clamp to avoid squota underflow
      btrfs: swallow btrfs_record_squota_delta() ENOENT

Robbie Ko (1):
      btrfs: mark file extent range dirty after converting prealloc extents

 fs/btrfs/extent_map.c |   4 +-
 fs/btrfs/file.c       |  11 ++++--
 fs/btrfs/fs.h         |   1 +
 fs/btrfs/inode.c      |   4 +-
 fs/btrfs/qgroup.c     | 101 +++++++++++++++++++++++++++++++++-----------------
 5 files changed, 83 insertions(+), 38 deletions(-)

             reply	other threads:[~2026-05-23 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 15:04 David Sterba [this message]
2026-05-24  0:07 ` [GIT PULL] Btrfs fixes for 7.1-rc5 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.1779547014.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