From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 7.1-rc4
Date: Fri, 15 May 2026 19:34:23 +0200 [thread overview]
Message-ID: <cover.1778865786.git.dsterba@suse.com> (raw)
Hi,
please pull the following fixes, thanks.
- fixup warning when allocating memory for readahead, __GFP_NOWARN was
accidentally dropped when setting mapping constraints
- in tracepoint of file sync, fix sleeping in atomic context when
handling dentries
- harden initial loading of block group on crafted/fuzzed images,
iterate all chunk mapping entries unconditionally
- fix freeing pages of submitted io after checking for errors
- fix incorrect inode size after remount when using fallocate KEEP_SIZE
mode (also requires disabled 'no-holes' feature)
----------------------------------------------------------------
The following changes since commit 82323b1a7088b7a5c3e528a5d634bff447fa286f:
btrfs: fix double-decrement of bytes_may_use in submit_one_async_extent() (2026-04-21 04:03: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-rc3-tag
for you to fetch changes up to c562ba61fc5e11798720acc1b172862158f1fa0b:
btrfs: fix incorrect i_size after remount caused by KEEP_SIZE prealloc gap (2026-05-08 00:32:08 +0200)
----------------------------------------------------------------
Calvin Owens (1):
btrfs: always pass __GFP_NOWARN from add_ra_bio_pages()
Filipe Manana (1):
btrfs: tracepoints: fix sleep while in atomic context in btrfs_sync_file()
Qu Wenruo (1):
btrfs: only release the dirty pages io tree after successful writes
Robbie Ko (1):
btrfs: fix incorrect i_size after remount caused by KEEP_SIZE prealloc gap
ZhengYuan Huang (1):
btrfs: fix check_chunk_block_group_mappings() to iterate all chunk maps
fs/btrfs/block-group.c | 23 ++++++++---------------
fs/btrfs/compression.c | 26 ++++++++++++++------------
fs/btrfs/disk-io.c | 1 +
fs/btrfs/inode.c | 28 ++++++++++++++++++++++++++++
fs/btrfs/transaction.c | 9 ++++-----
include/trace/events/btrfs.h | 4 +---
6 files changed, 56 insertions(+), 35 deletions(-)
next reply other threads:[~2026-05-15 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 17:34 David Sterba [this message]
2026-05-15 22:14 ` [GIT PULL] Btrfs fixes for 7.1-rc4 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.1778865786.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 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.