From: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/3] Misc refactoring of check_file_extent
Date: Thu, 13 Sep 2018 20:23:37 +0800 [thread overview]
Message-ID: <20180913122337.GH2790@fnst.localdomain> (raw)
In-Reply-To: <20180913120507.18197-1-nborisov@suse.com>
On Thu, Sep 13, 2018 at 03:05:04PM +0300, Nikolay Borisov wrote:
>While looking at check_file_extent I thought that the code might be a bit
>cleaner than it actually is and cleaner as well. The first patch factors out
>the code dealing with inline extents into a separate function aptly named
>check_file_extent_inline. This allows to remove some inline-specific variable
>from check_file_extent. Patch 2 just moves the final check in the new function
>into the already existing branch handling the !compressed case. Finally
>the check which detects unknown extent types is moved first in check_file_extent,
>followed by the code to handle inline extents and finally the existing code to
>handle regular/prealloc extents is left intact.
>
>This patchset brings no functional changes.
For the series,
Reviewed-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
--
Thanks,
Lu
>
>Nikolay Borisov (3):
> btrfs-progs: check: lowmem: Factor out inline extent checking code in
> its own function
> btrfs-progs: check: lowmem: Refactor extent len test in
> check_file_extent_inline
> btrfs-progs: check: lowmem: Refactor extent type checks in
> check_file_extent
>
> check/mode-lowmem.c | 151 ++++++++++++++++++++++++++------------------
> 1 file changed, 89 insertions(+), 62 deletions(-)
>
>--
>2.17.1
>
>
>
next prev parent reply other threads:[~2018-09-13 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 12:05 [PATCH 0/3] Misc refactoring of check_file_extent Nikolay Borisov
2018-09-13 12:05 ` [PATCH 1/3] btrfs-progs: check: lowmem: Factor out inline extent checking code in its own function Nikolay Borisov
2018-09-13 23:05 ` Qu Wenruo
2018-10-31 9:35 ` misono.tomohiro
2018-10-31 9:43 ` Nikolay Borisov
2018-10-31 17:19 ` David Sterba
2018-10-31 9:40 ` misono.tomohiro
2018-09-13 12:05 ` [PATCH 2/3] btrfs-progs: check: lowmem: Refactor extent len test in check_file_extent_inline Nikolay Borisov
2018-09-13 23:07 ` Qu Wenruo
2018-09-13 12:05 ` [PATCH 3/3] btrfs-progs: check: lowmem: Refactor extent type checks in check_file_extent Nikolay Borisov
2018-09-13 23:08 ` Qu Wenruo
2018-09-13 12:23 ` Lu Fengqi [this message]
2018-10-24 17:45 ` [PATCH 0/3] Misc refactoring of check_file_extent 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=20180913122337.GH2790@fnst.localdomain \
--to=lufq.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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).