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-rc7
Date: Thu, 15 May 2025 02:36:50 +0200 [thread overview]
Message-ID: <cover.1747268650.git.dsterba@suse.com> (raw)
Hi,
please pull a few more fixes, thanks.
- fix potential endless loop when discarding a block group when
disabling discard
- reinstate message when setting a large value of mount option 'commit'
- fix a folio leak when async extent submission fails
----------------------------------------------------------------
The following changes since commit 38e541051e1d19e8b1479a6af587a7884653e041:
btrfs: open code folio_index() in btree_clear_folio_dirty_tag() (2025-05-02 13:20:56 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.15-rc6-tag
for you to fetch changes up to 4ce2affc6ef9f84b4aebbf18bd5c57397b6024eb:
btrfs: add back warning for mount option commit values exceeding 300 (2025-05-12 21:39:34 +0200)
----------------------------------------------------------------
Boris Burkov (1):
btrfs: fix folio leak in submit_one_async_extent()
Filipe Manana (1):
btrfs: fix discard worker infinite loop after disabling discard
Kyoji Ogasawara (1):
btrfs: add back warning for mount option commit values exceeding 300
fs/btrfs/discard.c | 17 +++++++++++++++--
fs/btrfs/fs.h | 1 +
fs/btrfs/inode.c | 7 +++++++
fs/btrfs/super.c | 4 ++++
4 files changed, 27 insertions(+), 2 deletions(-)
next reply other threads:[~2025-05-15 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 0:36 David Sterba [this message]
2025-05-15 1:46 ` 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.1747268650.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
all inboxes | Powered by JetHome®