From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: <Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp>
Cc: <flrncrmr@gmail.com>, <linux-fsdevel@vger.kernel.org>,
"'Sungjong Seo'" <sj1557.seo@samsung.com>
Subject: RE: [PATCH] exfat: handle wrong stream entry size in exfat_readdir()
Date: Fri, 16 Jul 2021 13:44:47 +0900 [thread overview]
Message-ID: <000001d779fd$4e12ca20$ea385e60$@samsung.com> (raw)
In-Reply-To: <OSBPR01MB45357B200F44AF64D446D42790129@OSBPR01MB4535.jpnprd01.prod.outlook.com>
> > This patch check DataLength in stream
> > entry only if the type is ALLOC_NO_FAT_CHAIN and add the check ensure
> > that dentry offset does not exceed max dentries size(256 MB) to avoid
> > the circular FAT chain issue.
>
> I think it's preferable to add a 256MB check during dir-scan.(as I said in the previous) If you want
> to solve "the circular FAT chain issue", you should add it to other dir-scan loops.
> (exfat_search_empty_slot, exfat_check_dir_empty, exfat_count_dir_entries, etc ...).
>
> Also, the dir-scan loop may not terminate when TYPE_UNUSED is detected.
> Even if TYPE_UNUSED is detected, just break the inner for-loop will continue the outer while-loop, so
> the next cluster will be accessed.
> If we can't use DataLength for checking, we should check the contents more strictly instead.
>
> The current implementation has several similar dir-scan loops.
> These are similar logics and should be abstracted, if possible.
Can you send me the patch instead of just talking?
>
> BR
> Kohada Tetsuhiro <Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp>
prev parent reply other threads:[~2021-07-16 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210611004956epcas1p262dc7907165782173692d7cf9e571dfe@epcas1p2.samsung.com>
2021-06-11 0:40 ` [PATCH] exfat: handle wrong stream entry size in exfat_readdir() Namjae Jeon
2021-07-01 19:04 ` Chris Down
2021-07-01 23:34 ` Namjae Jeon
2021-07-05 7:04 ` Kohada.Tetsuhiro
2021-07-05 7:35 ` Namjae Jeon
2021-07-12 3:11 ` Kohada.Tetsuhiro
2021-07-15 9:39 ` Kohada.Tetsuhiro
2021-07-16 4:44 ` Namjae Jeon [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='000001d779fd$4e12ca20$ea385e60$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp \
--cc=flrncrmr@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sj1557.seo@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.