From: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Gwendal Grignou <gwendal@chromium.org>,
dlunev@chromium.org
Subject: Re: [PATCH] fat: ignore .. subdir and always add a link to dirs
Date: Thu, 22 Feb 2024 23:02:16 -0300 [thread overview]
Message-ID: <Zdf8qPN5h74MzCQh@quatroqueijos.cascardo.eti.br> (raw)
In-Reply-To: <87bk88oskz.fsf@mail.parknet.co.jp>
On Fri, Feb 23, 2024 at 10:52:12AM +0900, OGAWA Hirofumi wrote:
> Thadeu Lima de Souza Cascardo <cascardo@igalia.com> writes:
>
> > The tools used for creating images for the Lego Mindstrom EV3 are not
> > adding '.' and '..' entry in the 'Projects' directory.
> >
> > Without this fix, the kernel can not fill the inode structure for
> > 'Projects' directory.
> >
> > See https://github.com/microsoft/pxt-ev3/issues/980
> > And https://github.com/microsoft/uf2-linux/issues/6
> >
> > When counting the number of subdirs, ignore .. subdir and add one when
> > setting the initial link count for directories. This way, when .. is
> > present, it is still accounted for, and when neither . or .. are present, a
> > single link is still done, as it should, since this link would be the one
> > from the parent directory.
> >
> > With this fix applied, we can mount an image with such empty directories,
> > access them, create subdirectories and remove them.
>
> This looks like the bug of those tools, isn't it?
>
> Thanks.
> --
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Which they refused to fix, arguing that there are already filesystems out there
in the world like that. Also, there is argument that this works on Windows,
though I haven't been able to test this.
https://github.com/microsoft/pxt-ev3/issues/980
https://github.com/microsoft/uf2-linux/issues/6
Thanks.
Cascardo.
next prev parent reply other threads:[~2024-02-23 2:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 20:30 [PATCH] fat: ignore .. subdir and always add a link to dirs Thadeu Lima de Souza Cascardo
2024-02-23 1:52 ` OGAWA Hirofumi
2024-02-23 2:02 ` Thadeu Lima de Souza Cascardo [this message]
2024-02-23 8:27 ` OGAWA Hirofumi
2024-02-23 8:32 ` OGAWA Hirofumi
2024-02-23 9:58 ` Thadeu Lima de Souza Cascardo
2024-02-23 12:29 ` OGAWA Hirofumi
2024-02-23 13:16 ` Thadeu Lima de Souza Cascardo
2024-02-23 13:33 ` Thadeu Lima de Souza Cascardo
2024-02-28 1:42 ` Thadeu Lima de Souza Cascardo
2024-02-28 3:38 ` OGAWA Hirofumi
2024-02-28 9:10 ` Thadeu Lima de Souza Cascardo
2024-03-04 23:37 ` Thadeu Lima de Souza Cascardo
2024-03-05 4:14 ` OGAWA Hirofumi
2024-03-10 5:52 ` OGAWA Hirofumi
2024-03-10 10:14 ` Thadeu Lima de Souza Cascardo
2024-03-10 14:59 ` OGAWA Hirofumi
2024-03-13 7:58 ` Thadeu Lima de Souza Cascardo
2024-03-13 8:05 ` OGAWA Hirofumi
2024-03-13 8:41 ` Thadeu Lima de Souza Cascardo
2024-03-13 11:06 ` OGAWA Hirofumi
2024-03-13 11:16 ` Thadeu Lima de Souza Cascardo
2024-03-13 12:43 ` OGAWA Hirofumi
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=Zdf8qPN5h74MzCQh@quatroqueijos.cascardo.eti.br \
--to=cascardo@igalia.com \
--cc=dlunev@chromium.org \
--cc=gwendal@chromium.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).