public inbox for linux-btrfs@vger.kernel.org
 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 fro 6.19-rc8
Date: Thu, 29 Jan 2026 15:25:19 +0100	[thread overview]
Message-ID: <cover.1769696202.git.dsterba@suse.com> (raw)

Hi,

please pull two fixes for bugs with serious consequences. Thanks.

- fix leaked folio refcount on s390x when using hw zlib compression
  acceleration

- remove own threshold from ->writepages() which could collide with
  cgroup limits and lead to a deadlock when metadadata are not written
  because the amount is under the internal limit

----------------------------------------------------------------
The following changes since commit 34308187395ff01f2d54007eb8b222f843bdf445:

  btrfs: add extra device item checks at mount (2026-01-20 17:18:48 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.19-rc7-tag

for you to fetch changes up to 0d0f1314e8f86f5205f71f9e31e272a1d008e40b:

  btrfs: zlib: fix the folio leak on S390 hardware acceleration (2026-01-21 19:35:41 +0100)

----------------------------------------------------------------
Qu Wenruo (2):
      btrfs: do not strictly require dirty metadata threshold for metadata writepages
      btrfs: zlib: fix the folio leak on S390 hardware acceleration

 fs/btrfs/disk-io.c   | 22 ----------------------
 fs/btrfs/extent_io.c |  3 +--
 fs/btrfs/extent_io.h |  3 +--
 fs/btrfs/zlib.c      |  1 +
 4 files changed, 3 insertions(+), 26 deletions(-)

             reply	other threads:[~2026-01-29 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 14:25 David Sterba [this message]
2026-01-30  0:28 ` [GIT PULL] Btrfs fixes fro 6.19-rc8 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.1769696202.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