public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Sterba <dsterba@suse.com>
Cc: stable@vger.kernel.org, David Sterba <dsterba@suse.cz>,
	Wang Yugui <wangyugui@e16-tech.com>
Subject: Re: [PATCH] btrfs: fix backport of 2175bf57dc952 in 5.4.95
Date: Mon, 22 Feb 2021 13:39:12 +0100	[thread overview]
Message-ID: <YDOl8Ptkjgx/gOK9@kroah.com> (raw)
In-Reply-To: <20210222121639.30086-1-dsterba@suse.com>

On Mon, Feb 22, 2021 at 01:16:39PM +0100, David Sterba wrote:
> From: David Sterba <dsterba@suse.cz>
> 
> There's a mistake in backport of upstream commit 2175bf57dc95 ("btrfs:
> fix possible free space tree corruption with online conversion") as
> 5.4.95 commit e1ae9aab8029.
> 
> The enum value BTRFS_FS_FREE_SPACE_TREE_UNTRUSTED has been added to the
> wrong enum set, colliding with value of BTRFS_FS_QUOTA_ENABLE. This
> could cause problems during the tree conversion, where the quotas
> wouldn't be set up properly but the related code executed anyway due to
> the bit set.
> 
> Link: https://lore.kernel.org/linux-btrfs/20210219111741.95DD.409509F4@e16-tech.com
> Reported-by: Wang Yugui <wangyugui@e16-tech.com>
> CC: stable@vger.kernel.org # 5.4.95+
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
> 
> This is same fix that went to 5.10.x, with refreshed diff so it applies
> cleanly on 5.4.x and with updated references.

Now queued up, thanks.

greg k-h

      reply	other threads:[~2021-02-22 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 12:16 [PATCH] btrfs: fix backport of 2175bf57dc952 in 5.4.95 David Sterba
2021-02-22 12:39 ` Greg KH [this message]

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=YDOl8Ptkjgx/gOK9@kroah.com \
    --to=greg@kroah.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=stable@vger.kernel.org \
    --cc=wangyugui@e16-tech.com \
    /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