From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Cc: wqu@suse.com
Subject: Re: [PATCH] btrfs: tree-check: reduce stack consumption in check_dir_item
Date: Thu, 11 Jan 2018 09:14:26 +0800 [thread overview]
Message-ID: <52c544df-b1d7-4c6e-3069-374f55fe9c4e@gmx.com> (raw)
In-Reply-To: <20180110142851.27624-1-dsterba@suse.com>
[-- Attachment #1.1: Type: text/plain, Size: 1631 bytes --]
On 2018年01月10日 22:28, David Sterba wrote:
> I've noticed that the updated item checker stack consumption increased
> dramatically in 542f5385e20cf97447 ("btrfs: tree-checker: Add checker
> for dir item")
>
> tree-checker.c:check_leaf +552 (176 -> 728)
>
> The array is 255 bytes long, dynamic allocation would slow down the
> sanity checks so it's more reasonable to keep it on-stack. Moving the
> variable to the scope of use reduces the stack usage again
>
> tree-checker.c:check_leaf -264 (728 -> 464)
>
> Signed-off-by: David Sterba <dsterba@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> fs/btrfs/tree-checker.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/tree-checker.c b/fs/btrfs/tree-checker.c
> index 7c55e3ba5a6c..c3c8d48f6618 100644
> --- a/fs/btrfs/tree-checker.c
> +++ b/fs/btrfs/tree-checker.c
> @@ -259,7 +259,6 @@ static int check_dir_item(struct btrfs_root *root,
>
> di = btrfs_item_ptr(leaf, slot, struct btrfs_dir_item);
> while (cur < item_size) {
> - char namebuf[max(BTRFS_NAME_LEN, XATTR_NAME_MAX)];
> u32 name_len;
> u32 data_len;
> u32 max_name_len;
> @@ -342,6 +341,8 @@ static int check_dir_item(struct btrfs_root *root,
> */
> if (key->type == BTRFS_DIR_ITEM_KEY ||
> key->type == BTRFS_XATTR_ITEM_KEY) {
> + char namebuf[max(BTRFS_NAME_LEN, XATTR_NAME_MAX)];
> +
> read_extent_buffer(leaf, namebuf,
> (unsigned long)(di + 1), name_len);
> name_hash = btrfs_name_hash(namebuf, name_len);
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
prev parent reply other threads:[~2018-01-11 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 14:28 [PATCH] btrfs: tree-check: reduce stack consumption in check_dir_item David Sterba
2018-01-10 15:46 ` Josef Bacik
2018-01-11 1:14 ` Qu Wenruo [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=52c544df-b1d7-4c6e-3069-374f55fe9c4e@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.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;
as well as URLs for NNTP newsgroup(s).