From: Filipe Manana <fdmanana@gmail.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 5/6] btrfs: Simplify extent type check
Date: Tue, 6 Aug 2019 11:14:45 +0100 [thread overview]
Message-ID: <CAL3q7H6CPM-NMXw6eZQAs=k2C_vcG-i9gChHjuHU9FZvqRCZOw@mail.gmail.com> (raw)
In-Reply-To: <20190805144708.5432-6-nborisov@suse.com>
On Mon, Aug 5, 2019 at 3:47 PM Nikolay Borisov <nborisov@suse.com> wrote:
>
> Extent type can only be regular/prealloc/inline. The main branch of the
> 'if' already handles the first two, leaving the 'else' to handle inline.
> Furthermore, tree-checker ensures that leaf items are correct.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Filipe Manana <fdmanana@suse.com>
> ---
> fs/btrfs/inode.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index 8e24b7641247..6c3f9f3a7ed1 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -1502,18 +1502,14 @@ static noinline int run_delalloc_nocow(struct inode *inode,
> if (!btrfs_inc_nocow_writers(fs_info, disk_bytenr))
> goto out_check;
> nocow = true;
> - } else if (extent_type == BTRFS_FILE_EXTENT_INLINE) {
> - extent_end = found_key.offset +
> - btrfs_file_extent_ram_bytes(leaf, fi);
> - extent_end = ALIGN(extent_end,
> - fs_info->sectorsize);
> + } else {
> + extent_end = found_key.offset + ram_bytes;
> + extent_end = ALIGN(extent_end, fs_info->sectorsize);
> /* Skip extents outside of our requested range */
> if (extent_end <= start) {
> path->slots[0]++;
> goto next_slot;
> }
> - } else {
> - BUG();
> }
> out_check:
> /*
> --
> 2.17.1
>
--
Filipe David Manana,
“Whether you think you can, or you think you can't — you're right.”
next prev parent reply other threads:[~2019-08-06 10:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:47 [PATCH 0/6] Refactor nocow path Nikolay Borisov
2019-08-05 14:47 ` [PATCH 1/6] btrfs: Refactor run_delalloc_nocow Nikolay Borisov
2019-08-21 7:42 ` [PATCH v2 1/2] " Nikolay Borisov
2019-08-21 15:03 ` David Sterba
2019-08-05 14:47 ` [PATCH 2/6] btrfs: Improve comments around nocow path Nikolay Borisov
2019-08-06 10:09 ` Filipe Manana
2019-08-07 8:16 ` Nikolay Borisov
2019-08-07 8:26 ` Filipe Manana
2019-08-21 7:42 ` [PATCH v2 2/2] " Nikolay Borisov
2019-08-21 15:10 ` David Sterba
2019-08-05 14:47 ` [PATCH 3/6] btrfs: Simplify run_delalloc_nocow Nikolay Borisov
2019-08-06 9:01 ` Johannes Thumshirn
2019-08-05 14:47 ` [PATCH 4/6] btrfs: Streamline code in run_delalloc_nocow in case of inline extents Nikolay Borisov
2019-08-21 15:17 ` David Sterba
2019-08-05 14:47 ` [PATCH 5/6] btrfs: Simplify extent type check Nikolay Borisov
2019-08-06 10:14 ` Filipe Manana [this message]
2019-08-21 15:40 ` David Sterba
2019-08-21 23:47 ` Qu Wenruo
2019-08-22 5:58 ` Nikolay Borisov
2019-08-22 14:25 ` [PATCH] btrfs: Streamline code in run_delalloc_nocow Nikolay Borisov
2019-08-23 17:27 ` David Sterba
2019-08-05 14:47 ` [PATCH 6/6] btrfs: Remove BUG_ON from run_delalloc_nocow Nikolay Borisov
2019-08-06 10:34 ` Filipe Manana
2019-08-07 8:18 ` Nikolay Borisov
2019-08-21 15:55 ` David Sterba
2019-08-22 14:24 ` [PATCH v2] " Nikolay Borisov
2019-08-23 17:28 ` David Sterba
2019-08-19 16:42 ` [PATCH 0/6] Refactor nocow path David Sterba
2019-08-21 15:59 ` 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='CAL3q7H6CPM-NMXw6eZQAs=k2C_vcG-i9gChHjuHU9FZvqRCZOw@mail.gmail.com' \
--to=fdmanana@gmail.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).