From: Josef Bacik <jbacik@fb.com>
To: <dsterba@suse.cz>, Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>,
<linux-btrfs@vger.kernel.org>, <clm@fb.com>, <dsterba@suse.com>
Subject: Re: [PATCH] btrfs: do not decrease bytes_may_use when replaying extents
Date: Thu, 1 Sep 2016 13:30:05 -0400 [thread overview]
Message-ID: <a06cbb7f-4337-9ecc-9ba7-fe3cb990110c@fb.com> (raw)
In-Reply-To: <20160901153629.GT16983@twin.jikos.cz>
On 09/01/2016 11:36 AM, David Sterba wrote:
> CC Josef. It's a followup of patch that went to 4.8-rc4 so we'd better
> get it to 4.8.
>
> On Fri, Aug 26, 2016 at 11:33:14AM +0800, Wang Xiaoguang wrote:
>> When replaying extents, there is no need to update bytes_may_use
>> in btrfs_alloc_logged_file_extent(), otherwise it'll trigger a
>> WARN_ON about bytes_may_use.
>>
>> Fixes: ("btrfs: update btrfs_space_info's bytes_may_use timely")
>> Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Thanks,
Josef
prev parent reply other threads:[~2016-09-01 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 3:33 [PATCH] btrfs: do not decrease bytes_may_use when replaying extents Wang Xiaoguang
2016-09-01 15:36 ` David Sterba
2016-09-01 17:30 ` Josef Bacik [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=a06cbb7f-4337-9ecc-9ba7-fe3cb990110c@fb.com \
--to=jbacik@fb.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangxg.fnst@cn.fujitsu.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).