From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Subject: Re: [PATCH 0/3] fs/fat: fix handling of full disk
Date: Thu, 14 Jul 2022 09:46:05 +0900 [thread overview]
Message-ID: <20220714004605.GC42596@laputa> (raw)
In-Reply-To: <20220712223314.20530-1-xypron.glpk@gmx.de>
On Tue, Jul 12, 2022 at 10:33:11PM +0000, Heinrich Schuchardt wrote:
> Currently we have two functions with redundant coding to find an empty
> cluster:
>
> * find_empty_cluster() seeks from the beginning of the FAT table
> * determine_fatent() seeks after a given entry
>
> Both do not detect the end of the FAT table correctly and return an invalid
> cluster number if no empty entry if found.
>
> Correctly determine empty FAT entries and full disk correctly.
I hope that you add a test for this specific corner case.
Thanks,
-Takahiro Akashi
> Carve out a function for creating directory entries to avoid code
> duplication.
>
> Heinrich Schuchardt (3):
> fs: fat: finding an empty FAT cluster
> fs: fat: determine_fatent() error handling
> fs: fat: carve out fat_create_dir_entry()
>
> fs/fat/fat_write.c | 161 ++++++++++++++++++++++-----------------------
> 1 file changed, 79 insertions(+), 82 deletions(-)
>
> --
> 2.30.2
>
prev parent reply other threads:[~2022-07-14 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 22:33 [PATCH 0/3] fs/fat: fix handling of full disk Heinrich Schuchardt
2022-07-12 22:33 ` [PATCH 1/3] fs: fat: finding an empty FAT cluster Heinrich Schuchardt
2022-07-14 0:39 ` AKASHI Takahiro
2022-07-12 22:33 ` [PATCH 2/3] fs: fat: determine_fatent() error handling Heinrich Schuchardt
2022-07-12 22:33 ` [PATCH 3/3] fs: fat: carve out fat_create_dir_entry() Heinrich Schuchardt
2022-07-14 0:43 ` AKASHI Takahiro
2022-07-14 0:46 ` AKASHI Takahiro [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=20220714004605.GC42596@laputa \
--to=takahiro.akashi@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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.