From: Qu WenRuo <wqu@suse.com>
To: Nikolay Borisov <nborisov@suse.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 1/6] btrfs-progs: check: Export btrfs_type_to_imode
Date: Tue, 24 Sep 2019 09:19:55 +0000 [thread overview]
Message-ID: <3d3cfcfb-d55b-a0fa-c182-a52c138c6b65@suse.com> (raw)
In-Reply-To: <8bce1985-0bd7-2476-8276-530ab08a00d6@suse.com>
On 2019/9/24 下午4:41, Nikolay Borisov wrote:
>
>
> On 12.09.19 г. 6:11 ч., Qu Wenruo wrote:
>> This function will be later used by common mode code, so export it.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>
> Reviewed-by: Nikolay Borisov <nborisov@suse.com> but see one nit below.
>
>> ---
>> check/main.c | 15 ---------------
>> check/mode-common.h | 15 +++++++++++++++
>> 2 files changed, 15 insertions(+), 15 deletions(-)
>>
>> diff --git a/check/main.c b/check/main.c
>> index 2e16b4e6f05b..902279740589 100644
>> --- a/check/main.c
>> +++ b/check/main.c
>> @@ -2448,21 +2448,6 @@ out:
>> return ret;
>> }
>>
>> -static u32 btrfs_type_to_imode(u8 type)
>> -{
>> - static u32 imode_by_btrfs_type[] = {
>> - [BTRFS_FT_REG_FILE] = S_IFREG,
>> - [BTRFS_FT_DIR] = S_IFDIR,
>> - [BTRFS_FT_CHRDEV] = S_IFCHR,
>> - [BTRFS_FT_BLKDEV] = S_IFBLK,
>> - [BTRFS_FT_FIFO] = S_IFIFO,
>> - [BTRFS_FT_SOCK] = S_IFSOCK,
>> - [BTRFS_FT_SYMLINK] = S_IFLNK,
>> - };
>> -
>> - return imode_by_btrfs_type[(type)];
>> -}
>> -
>> static int repair_inode_no_item(struct btrfs_trans_handle *trans,
>> struct btrfs_root *root,
>> struct btrfs_path *path,
>> diff --git a/check/mode-common.h b/check/mode-common.h
>> index 161b84a8deb0..6c8d6d7578a6 100644
>> --- a/check/mode-common.h
>> +++ b/check/mode-common.h
>> @@ -156,4 +156,19 @@ static inline bool is_valid_imode(u32 imode)
>> }
>>
>> int recow_extent_buffer(struct btrfs_root *root, struct extent_buffer *eb);
>> +
>> +static inline u32 btrfs_type_to_imode(u8 type)
>> +{
>> + static u32 imode_by_btrfs_type[] = {
>> + [BTRFS_FT_REG_FILE] = S_IFREG,
>> + [BTRFS_FT_DIR] = S_IFDIR,
>> + [BTRFS_FT_CHRDEV] = S_IFCHR,
>> + [BTRFS_FT_BLKDEV] = S_IFBLK,
>> + [BTRFS_FT_FIFO] = S_IFIFO,
>> + [BTRFS_FT_SOCK] = S_IFSOCK,
>> + [BTRFS_FT_SYMLINK] = S_IFLNK,
>> + };
>
> nit: If the array is defined in a function in a header this means it
> will be copied to every object file this header is included so it will
> result in a minor bloat of size. It might better to have it defined in
> check/main.c and have it declared extern in mode-common.h
I'm wondering what happens in the final binary.
IIRC there should be only one copy of the static const array in .data
segment.
So that should be mostly OK I guess?
Thanks,
Qu
>
>> +
>> + return imode_by_btrfs_type[(type)];
>> +}
>> #endif
>>
next prev parent reply other threads:[~2019-09-24 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 3:11 [PATCH v2 0/6] btrfs-progs: check: Repair invalid inode mode in subvolume trees Qu Wenruo
2019-09-12 3:11 ` [PATCH v3 1/6] btrfs-progs: check: Export btrfs_type_to_imode Qu Wenruo
2019-09-24 8:41 ` Nikolay Borisov
2019-09-24 9:19 ` Qu WenRuo [this message]
2019-09-12 3:11 ` [PATCH v3 2/6] btrfs-progs: check/common: Introduce a function to find imode using info from INODE_REF item Qu Wenruo
2019-09-12 3:11 ` [PATCH v3 3/6] btrfs-progs: check/common: Make repair_imode_common() to handle inodes in subvolume trees Qu Wenruo
2019-09-12 3:11 ` [PATCH v3 4/6] btrfs-progs: check/lowmem: Repair bad imode early Qu Wenruo
2019-09-12 3:11 ` [PATCH v3 5/6] btrfs-progs: check/original: Fix inode mode in subvolume trees Qu Wenruo
2019-09-12 3:11 ` [PATCH v3 6/6] btrfs-progs: tests/fsck: Add new images for inode mode repair functionality Qu Wenruo
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=3d3cfcfb-d55b-a0fa-c182-a52c138c6b65@suse.com \
--to=wqu@suse.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).