From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Qu Wenruo <wqu@suse.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] btrfs: scrub avoid use-after-free when chunk length is not 64K aligned
Date: Wed, 17 Jan 2024 07:54:42 +0000 [thread overview]
Message-ID: <7810799d-23c3-4a43-905b-e5112cd7d6e9@wdc.com> (raw)
In-Reply-To: <cover.1705449249.git.wqu@suse.com>
On 17.01.24 01:33, Qu Wenruo wrote:
> [Changelog]
> v2:
> - Split out the RST code change
> So that backport can happen more smoothly.
> Furthermore, the RST specific part is really just a small enhancement.
> As RST would always do the btrfs_map_block(), even if we have a
> corrupted extent item beyond chunk, it would be properly caught,
> thus at most false alerts, no real use-after-free can happen after
> the first patch.
>
> - Slight update on the commit message of the first patch
> Fix a copy-and-paste error of the number used to calculate the chunk
> end.
> Remove the RST scrub part, as we won't do any RST fix (although
> it would still sliently fix RST, since both RST and regular scrub
> share the same endio function)
>
> There is a bug report about use-after-free during scrub and crash the
> system.
> It turns out to be a chunk whose lenght is not 64K aligned causing the
> problem.
>
> The first patch would be the proper fix, needs to be backported to all
> kernel using newer scrub interface.
>
> The 2nd patch is a small enhancement for RST scrub, inspired by the
> above bug, which doesn't really need to be backported.
>
> Qu Wenruo (2):
> btrfs: scrub: avoid use-after-free when chunk length is not 64K
> aligned
> btrfs: scrub: limit RST scrub to chunk boundary
>
> fs/btrfs/scrub.c | 36 +++++++++++++++++++++++++++++-------
> 1 file changed, 29 insertions(+), 7 deletions(-)
>
For the series,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
One more thing I personally would add (as a 3rd patch that doesn't need
to get backported to stable) is this:
diff --git a/fs/btrfs/scrub.c b/fs/btrfs/scrub.c
index 0123d2728923..046fdf8f6773 100644
--- a/fs/btrfs/scrub.c
+++ b/fs/btrfs/scrub.c
@@ -1641,14 +1641,23 @@ static void scrub_reset_stripe(struct
scrub_stripe *stripe)
}
}
+static unsigned int scrub_nr_stripe_sectors(struct scrub_stripe *stripe)
+{
+ struct btrfs_fs_info *fs_info = stripe->bg->fs_info;
+ struct btrfs_block_group *bg = stripe->bg;
+ u64 bg_end = bg->start + bg->length;
+ unsigned int nr_sectors;
+
+ nr_sectors = min(BTRFS_STRIPE_LEN, bg_end - stripe->logical);
+ return nr_sectors >> fs_info->sectorsize_bits;
+}
+
static void scrub_submit_extent_sector_read(struct scrub_ctx *sctx,
struct scrub_stripe *stripe)
{
struct btrfs_fs_info *fs_info = stripe->bg->fs_info;
struct btrfs_bio *bbio = NULL;
- unsigned int nr_sectors = min(BTRFS_STRIPE_LEN, stripe->bg->start +
- stripe->bg->length -
stripe->logical) >>
- fs_info->sectorsize_bits;
+ unsigned int nr_sectors = scrub_nr_stripe_sectors(stripe);
u64 stripe_len = BTRFS_STRIPE_LEN;
int mirror = stripe->mirror_num;
int i;
@@ -1718,9 +1727,7 @@ static void scrub_submit_initial_read(struct
scrub_ctx *sctx,
{
struct btrfs_fs_info *fs_info = sctx->fs_info;
struct btrfs_bio *bbio;
- unsigned int nr_sectors = min(BTRFS_STRIPE_LEN, stripe->bg->start +
- stripe->bg->length -
stripe->logical) >>
- fs_info->sectorsize_bits;
+ unsigned int nr_sectors = scrub_nr_stripe_sectors(stripe);
int mirror = stripe->mirror_num;
ASSERT(stripe->bg);
Sorry for the complete whitespace damage, but I think you get the point.
next prev parent reply other threads:[~2024-01-17 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 0:32 [PATCH v2 0/2] btrfs: scrub avoid use-after-free when chunk length is not 64K aligned Qu Wenruo
2024-01-17 0:32 ` [PATCH v2 1/2] btrfs: scrub: " Qu Wenruo
2024-01-17 0:32 ` [PATCH v2 2/2] btrfs: scrub: limit RST scrub to chunk boundary Qu Wenruo
2024-01-17 7:54 ` Johannes Thumshirn [this message]
2024-01-17 7:57 ` [PATCH v2 0/2] btrfs: scrub avoid use-after-free when chunk length is not 64K aligned Qu Wenruo
2024-01-17 8:09 ` Johannes Thumshirn
2024-01-17 17:17 ` David Sterba
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=7810799d-23c3-4a43-905b-e5112cd7d6e9@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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