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.15-rc5
Date: Wed, 30 Apr 2025 16:16:30 +0200 [thread overview]
Message-ID: <cover.1746021929.git.dsterba@suse.com> (raw)
Hi,
please pull a few short fixes, thanks.
- fix potential inode leak in iget() after memory allocation failure
- in subpage mode, fix extent buffer bitmap iteration when writing
out dirty sectors
- fix range calculation when falling back to COW for a NOCOW file
----------------------------------------------------------------
The following changes since commit 866bafae59ecffcf1840d846cd79740be29f21d6:
btrfs: zoned: skip reporting zone for new block group (2025-04-17 11:57:25 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.15-rc4-tag
for you to fetch changes up to e08e49d986f82c30f42ad0ed43ebbede1e1e3739:
btrfs: adjust subpage bit start based on sectorsize (2025-04-23 08:42:10 +0200)
----------------------------------------------------------------
Dave Chen (1):
btrfs: fix COW handling in run_delalloc_nocow()
Josef Bacik (1):
btrfs: adjust subpage bit start based on sectorsize
Penglei Jiang (1):
btrfs: fix the inode leak in btrfs_iget()
fs/btrfs/extent_io.c | 2 +-
fs/btrfs/inode.c | 13 ++++++++-----
2 files changed, 9 insertions(+), 6 deletions(-)
next reply other threads:[~2025-04-30 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 14:16 David Sterba [this message]
2025-04-30 18:12 ` [GIT PULL] Btrfs fixes for 6.15-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.1746021929.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.