From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: "'Chris Mason'" <clm@fb.com>,
"'linux-btrfs'" <linux-btrfs@vger.kernel.org>, <dsterba@suse.cz>
Subject: RE: [PATCH] Btrfs: fix allocation size calculations in alloc_btrfs_bio
Date: Mon, 23 Feb 2015 09:33:13 +0800 [thread overview]
Message-ID: <002101d04f08$b2eb4480$18c1cd80$@cn.fujitsu.com> (raw)
In-Reply-To: <20150220015930.GA28726@ret.masoncoding.com>
Hi, Chris Mason
* From: Chris Mason [mailto:clm@fb.com]
> Sent: Friday, February 20, 2015 10:00 AM
> To: linux-btrfs; Zhao Lei; dsterba@suse.cz
> Subject: [PATCH] Btrfs: fix allocation size calculations in alloc_btrfs_bio
>
> Since commit 8e5cfb55d3f (Btrfs: Make raid_map array be inlined in btrfs_bio
> structure), the raid map array is allocated along with the btrfs bio in
> alloc_btrfs_bio. The calculation used to decide how much we need to allocate
> was using the wrong parameter passed into the allocation function.
>
> The passed in real_stripes will be zero if a target replace operation is not
> currently running. We want to use total_stripes instead.
>
Sorry, my bad.
Thanks
Zhaolei
> Signed-off-by: Chris Mason <clm@fb.com>
> Reported-by: Dave Sterba <dsterba@suse.cz>
>
> ---
> fs/btrfs/volumes.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c index cd4d131..8222f6f
> 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -4903,10 +4903,17 @@ static void sort_parity_stripes(struct btrfs_bio
> *bbio, int num_stripes) static struct btrfs_bio *alloc_btrfs_bio(int
> total_stripes, int real_stripes) {
> struct btrfs_bio *bbio = kzalloc(
> + /* the size of the btrfs_bio */
> sizeof(struct btrfs_bio) +
> + /* plus the variable array for the stripes */
> sizeof(struct btrfs_bio_stripe) * (total_stripes) +
> + /* plus the variable array for the tgt dev */
> sizeof(int) * (real_stripes) +
> - sizeof(u64) * (real_stripes),
> + /*
> + * plus the raid_map, which includes both the tgt dev
> + * and the stripes
> + */
> + sizeof(u64) * (total_stripes),
> GFP_NOFS);
> if (!bbio)
> return NULL;
> --
> 1.8.1
prev parent reply other threads:[~2015-02-23 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 1:59 [PATCH] Btrfs: fix allocation size calculations in alloc_btrfs_bio Chris Mason
2015-02-20 14:35 ` David Sterba
2015-02-20 14:37 ` Chris Mason
2015-02-23 1:33 ` Zhao Lei [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='002101d04f08$b2eb4480$18c1cd80$@cn.fujitsu.com' \
--to=zhaolei@cn.fujitsu.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox