From: David Sterba <dsterba@suse.cz>
To: stable@vger.kernel.org
Subject: Two more btrfs fixes for 5.16.x
Date: Fri, 4 Mar 2022 18:12:45 +0100 [thread overview]
Message-ID: <20220304171245.GA12643@suse.cz> (raw)
Hi,
there are two more patches that did not have the CC: stable tag from the
recent series to fix defrag in btrfs. Please add them to 5.16 queue,
both apply cleanly, thanks.
d5633b0dee02 btrfs: defrag: bring back the old file extent search behavior
199257a78bb0 btrfs: defrag: don't use merged extent map for their generation check
next reply other threads:[~2022-03-04 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 17:12 David Sterba [this message]
2022-03-05 10:37 ` Two more btrfs fixes for 5.16.x Greg KH
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=20220304171245.GA12643@suse.cz \
--to=dsterba@suse.cz \
--cc=stable@vger.kernel.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.