Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tetsuhiro Kohada <kohada.t2@gmail.com>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: kohada.tetsuhiro@dc.mitsubishielectric.co.jp,
mori.takahiro@ab.mitsubishielectric.co.jp,
motai.hirotaka@aj.mitsubishielectric.co.jp,
'Sungjong Seo' <sj1557.seo@samsung.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] exfat: integrates dir-entry getting and validation
Date: Wed, 12 Aug 2020 22:25:34 +0900 [thread overview]
Message-ID: <ca3b2b52-1abc-939c-aa11-8c7d12e4eb2e@gmail.com> (raw)
In-Reply-To: <003c01d66edc$edbb1690$c93143b0$@samsung.com>
Thank you for your reply.
>> @@ -171,7 +174,9 @@ struct exfat_entry_set_cache {
>> unsigned int start_off;
>> int num_bh;
>> struct buffer_head *bh[DIR_CACHE_SIZE];
>> - unsigned int num_entries;
>> + int num_entries;
>> + struct exfat_de_file *de_file;
>> + struct exfat_de_stream *de_stream;
> I prefer to assign validated entries to **de and use it using enum value.
> struct exfat_dentry **de;
I've tried several implementations that add a struct exfat_dentry type.(*de0 & *de1; *de[2]; etc...)
The problem with the struct exfat_dentry type is that it is too flexible for type.
This means weak typing.
Therefore, when using them,
de[XXX_FILE]->dentry.file.zzz ...
It is necessary to re-specify the type. (against the DRY principle)
Strong typing prevents use with wrong type, at compiling.
I think the approach of using de_file/de_stream could be strongly typed.
I don't think we need excessive flexibility.
BR
---
Tetsuhiro Kohada <kohada.t2@gmail.com>
next prev parent reply other threads:[~2020-08-12 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200806010249epcas1p18fd6e3febad305975b43e1b55b56bcae@epcas1p1.samsung.com>
2020-08-06 1:02 ` Tetsuhiro Kohada
2020-08-08 16:35 ` Sungjong Seo
2020-08-10 6:10 ` Namjae Jeon
2020-08-12 13:25 ` Tetsuhiro Kohada [this message]
2020-08-21 6:53 ` Namjae Jeon
2020-08-25 8:21 ` Tetsuhiro Kohada
2020-08-26 1:03 ` Namjae Jeon
2020-08-26 2:56 ` Tetsuhiro Kohada
2020-08-26 4:19 ` Namjae Jeon
2020-08-26 6:07 ` Tetsuhiro Kohada
2020-08-26 7:32 ` Namjae Jeon
2020-08-27 9:59 ` Tetsuhiro Kohada
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=ca3b2b52-1abc-939c-aa11-8c7d12e4eb2e@gmail.com \
--to=kohada.t2@gmail.com \
--cc=kohada.tetsuhiro@dc.mitsubishielectric.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mori.takahiro@ab.mitsubishielectric.co.jp \
--cc=motai.hirotaka@aj.mitsubishielectric.co.jp \
--cc=namjae.jeon@samsung.com \
--cc=sj1557.seo@samsung.com \
--subject='Re: [PATCH v3] exfat: integrates dir-entry getting and validation' \
/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
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).