linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'David Disseldorp'" <ddiss@suse.de>
Cc: "'Sungjong Seo'" <sj1557.seo@samsung.com>,
	"'Namjae Jeon'" <linkinjeon@kernel.org>,
	<linux-fsdevel@vger.kernel.org>
Subject: RE: [PATCH 0/2] exfat: allow access to paths with trailing dots
Date: Mon, 23 Aug 2021 13:48:17 +0900	[thread overview]
Message-ID: <004e01d797da$16fe0590$44fa10b0$@samsung.com> (raw)
In-Reply-To: <20210820151214.37742aad@suse.de>

> Date: Wed, 18 Aug 2021 13:11:21 +0200
> From: David Disseldorp <ddiss@suse.de>
> To: linux-fsdevel@vger.kernel.org
> Subject: [PATCH 0/2] exfat: allow access to paths with trailing dots
> 
> 
Hi David,
> This patchset adds a new exfat "keeptail" mount option, which allows users to resolve paths carrying
> trailing period '.' characters.
> I'm not a huge fan of "keeptail" as an option name, but couldn't think of anything better.
We are concerning that this mount option allow to create the filename that
contain trailing period. It will cause the compatibility issues with windows.
I think compatibility with windows is more important than fuse-exfat.

Can we only allow those files to be accessed and prevented from being created?
> 
> Feedback appreciated.

Thanks!
> 
> Cheers, David
> 
> --
> 
>  fs/exfat/exfat_fs.h |  3 ++-
>  fs/exfat/namei.c    | 25 ++++++++++++++-----------
>  fs/exfat/super.c    |  7 +++++++
>  3 files changed, 23 insertions(+), 12 deletions(-)



       reply	other threads:[~2021-08-23  4:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210820131220epcas1p1e97adf5dfc5125571733d42d5d71110c@epcas1p1.samsung.com>
     [not found] ` <20210820151214.37742aad@suse.de>
2021-08-23  4:48   ` Namjae Jeon [this message]
2021-08-18 11:11 [PATCH 0/2] exfat: allow access to paths with trailing dots David Disseldorp
2021-08-18 12:48 ` Christian Brauner
2021-08-18 16:40   ` David Disseldorp
2021-08-18 17:49     ` Christian Brauner

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='004e01d797da$16fe0590$44fa10b0$@samsung.com' \
    --to=namjae.jeon@samsung.com \
    --cc=ddiss@suse.de \
    --cc=linkinjeon@kernel.org \
    --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 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).