From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Gwendal Grignou <gwendal@chromium.org>,
dlunev@chromium.org
Subject: Re: [PATCH v2 2/2] fat: always use dir_emit_dots and ignore . and .. entries
Date: Wed, 26 Jun 2024 06:47:15 +0900 [thread overview]
Message-ID: <871q4kae58.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <20240625175133.922758-3-cascardo@igalia.com> (Thadeu Lima de Souza Cascardo's message of "Tue, 25 Jun 2024 14:51:33 -0300")
Thadeu Lima de Souza Cascardo <cascardo@igalia.com> writes:
> Instead of only using dir_emit_dots for the root inode and explictily
> requiring the . and .. entries to emit them, use dir_emit_dots for all
> directories.
>
> That allows filesystems with directories without the . or .. entries to
> still show them.
Unacceptable to change the correct behavior to broken format. And
unlikely break the userspace, however this still has the user visible
change of seek pos.
Thanks.
> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
> ---
> fs/fat/dir.c | 24 +++++++++---------------
> 1 file changed, 9 insertions(+), 15 deletions(-)
>
> diff --git a/fs/fat/dir.c b/fs/fat/dir.c
> index 4e4a359a1ea3..e70781569de5 100644
> --- a/fs/fat/dir.c
> +++ b/fs/fat/dir.c
> @@ -583,15 +583,14 @@ static int __fat_readdir(struct inode *inode, struct file *file,
> mutex_lock(&sbi->s_lock);
>
> cpos = ctx->pos;
> - /* Fake . and .. for the root directory. */
> - if (inode->i_ino == MSDOS_ROOT_INO) {
> - if (!dir_emit_dots(file, ctx))
> - goto out;
> - if (ctx->pos == 2) {
> - fake_offset = 1;
> - cpos = 0;
> - }
> +
> + if (!dir_emit_dots(file, ctx))
> + goto out;
> + if (ctx->pos == 2) {
> + fake_offset = 1;
> + cpos = 0;
> }
> +
> if (cpos & (sizeof(struct msdos_dir_entry) - 1)) {
> ret = -ENOENT;
> goto out;
> @@ -671,13 +670,8 @@ static int __fat_readdir(struct inode *inode, struct file *file,
> if (fake_offset && ctx->pos < 2)
> ctx->pos = 2;
>
> - if (!memcmp(de->name, MSDOS_DOT, MSDOS_NAME)) {
> - if (!dir_emit_dot(file, ctx))
> - goto fill_failed;
> - } else if (!memcmp(de->name, MSDOS_DOTDOT, MSDOS_NAME)) {
> - if (!dir_emit_dotdot(file, ctx))
> - goto fill_failed;
> - } else {
> + if (memcmp(de->name, MSDOS_DOT, MSDOS_NAME) &&
> + memcmp(de->name, MSDOS_DOTDOT, MSDOS_NAME)) {
> unsigned long inum;
> loff_t i_pos = fat_make_i_pos(sb, bh, de);
> struct inode *tmp = fat_iget(sb, i_pos);
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2024-06-25 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 17:51 [PATCH v2 0/2] fat: add support for directories without . and .. entries Thadeu Lima de Souza Cascardo
2024-06-25 17:51 ` [PATCH v2 1/2] fat: ignore . and .. subdirs and always add links to dirs Thadeu Lima de Souza Cascardo
2024-06-25 17:51 ` [PATCH v2 2/2] fat: always use dir_emit_dots and ignore . and .. entries Thadeu Lima de Souza Cascardo
2024-06-25 21:47 ` OGAWA Hirofumi [this message]
2024-06-26 19:46 ` Thadeu Lima de Souza Cascardo
2024-06-26 20:10 ` OGAWA Hirofumi
2024-06-27 12:51 ` Thadeu Lima de Souza Cascardo
2024-06-27 15:28 ` 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=871q4kae58.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=cascardo@igalia.com \
--cc=dlunev@chromium.org \
--cc=gwendal@chromium.org \
--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