public inbox for linux-kernel@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 fix for 5.14-rc
Date: Thu, 26 Aug 2021 12:15:55 +0200	[thread overview]
Message-ID: <cover.1629897022.git.dsterba@suse.com> (raw)

Hi,

here's one more fix that I think qualifies for a late merge. It's a
revert of a one-liner fix that meanwhile got backported to stable
kernels and we got reports from users.

The broken fix prevents creating compressed inline extents, which could
be noticeable on space consumption.

Technically it's a regression as the patch was merged in 5.14-rc1
but got propagated to several stable kernels and has higher exposure
than a "typical" development cycle bug.

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 3f79f6f6247c83f448c8026c3ee16d4636ef8d4f:

  btrfs: prevent rename2 from exchanging a subvol with a directory from different parents (2021-08-16 13:33:23 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 4e9655763b82a91e4c341835bb504a2b1590f984:

  Revert "btrfs: compression: don't try to compress if we don't have enough pages" (2021-08-25 15:08:19 +0200)

----------------------------------------------------------------
Qu Wenruo (1):
      Revert "btrfs: compression: don't try to compress if we don't have enough pages"

 fs/btrfs/inode.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2021-08-26 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 10:15 David Sterba [this message]
2021-08-26 18:52 ` [GIT PULL] Btrfs fix for 5.14-rc 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.1629897022.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