From: Li Zefan <lizf@cn.fujitsu.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: free bitmaps properly when evicting the cache
Date: Wed, 20 Apr 2011 16:42:18 +0800 [thread overview]
Message-ID: <4DAE9C6A.30006@cn.fujitsu.com> (raw)
In-Reply-To: <1303158320-29058-1-git-send-email-josef@redhat.com>
Josef Bacik wrote:
> If our space cache is wrong, we do the right thing and free up everything that
> we loaded, however we don't reset the total_bitmaps counter or the thresholds or
> anything. So in btrfs_remove_free_space_cache make sure to call free_bitmap()
> if it's a bitmap, this will keep us from panicing when we check to make sure we
> don't have too many bitmaps. Thanks,
>
> Signed-off-by: Josef Bacik <josef@redhat.com>
Reviewed-by: Li Zefan <lizf@cn.fujitsu.com>
prev parent reply other threads:[~2011-04-20 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 20:25 [PATCH] Btrfs: free bitmaps properly when evicting the cache Josef Bacik
2011-04-20 8:42 ` Li Zefan [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=4DAE9C6A.30006@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=josef@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).