The Linux Kernel Mailing List
 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.14-rc5
Date: Tue, 25 Feb 2025 17:12:34 +0100	[thread overview]
Message-ID: <cover.1740498490.git.dsterba@suse.com> (raw)

Hi,

please pull a few more fixes. Thanks.

- extent map shrinker fixes
  - fix potential use after free accessing an inode to reach fs_info,
    the shrinker could do iput() in the meantime
  - skip unnecessary scanning of inodes without extent maps
  - do direct iput(), no need for indirection via workqueue

- in block < page mode, fix race when extending i_size in buffered mode

- fix minor memory leak in selftests

- print descriptive error message when seeding device is not found

----------------------------------------------------------------
The following changes since commit da2dccd7451de62b175fb8f0808d644959e964c7:

  btrfs: fix hole expansion when writing at an offset beyond EOF (2025-02-11 23:09:03 +0100)

are available in the Git repository at:

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

for you to fetch changes up to efa11fd269c139e29b71ec21bc9c9c0063fde40d:

  btrfs: fix data overwriting bug during buffered write when block size < page size (2025-02-21 09:32:24 +0100)

----------------------------------------------------------------
David Disseldorp (1):
      btrfs: selftests: fix btrfs_test_delayed_refs() leak of transaction

Filipe Manana (3):
      btrfs: fix use-after-free on inode when scanning root during em shrinking
      btrfs: skip inodes without loaded extent maps when shrinking extent maps
      btrfs: do regular iput instead of delayed iput during extent map shrinking

Qu Wenruo (2):
      btrfs: output an error message if btrfs failed to find the seed fsid
      btrfs: fix data overwriting bug during buffered write when block size < page size

 fs/btrfs/extent_map.c               | 83 ++++++++++++++++++++++++++-----------
 fs/btrfs/file.c                     |  9 +++-
 fs/btrfs/tests/delayed-refs-tests.c |  1 +
 fs/btrfs/volumes.c                  |  6 ++-
 4 files changed, 73 insertions(+), 26 deletions(-)

             reply	other threads:[~2025-02-25 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 16:12 David Sterba [this message]
2025-02-25 17:52 ` [GIT PULL] Btrfs fixes for 6.14-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.1740498490.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