From: "Pádraig Brady" <P@draigBrady.com>
To: Kamil Dudka <kdudka@redhat.com>
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH] mountlist: recognize more file system types as remote
Date: Tue, 3 Nov 2020 14:08:01 +0000 [thread overview]
Message-ID: <6e5f76f1-e958-68d3-db7b-3703ec36b506@draigBrady.com> (raw)
In-Reply-To: <2702655.Y6S9NjorxK@nbkamil>
On 03/11/2020 08:31, Kamil Dudka wrote:
> On Tuesday, October 27, 2020 10:23:15 PM CET Pádraig Brady wrote:
>> Sync "remote" file systems from stat.c in coreutils.
>> Note we only consider file systems that do not use host:resource
>> mount source. I.e. those that don't generally use a colon when
>> mounting, as that case is already considered. Searching for
>> "<fstype> /etc/fstab" was informative for identifying these.
>> The full list of "remote" file systems in coreutils is currently:
>> acfs afs ceph cifs coda fhgfs fuseblk fusectl
>> gfs gfs2 gpfs ibrix k-afs lustre novell nfs nfsd
>> ocfs2 panfs prl_fs smb smb2 snfs vboxsf vmhgfs vxfs
>> Note also we include virtual machine file systems,
>> as though they may not be distributed to separate hosts,
>> they're remote to the current kernel.
>>
>> * lib/mountlist.c (ME_REMOTE): Sync previously unconsidered
>> "remote" file systems from stat.c in coreutils.
>
> Looks good to me.
>
> Kamil
>
>> ---
>> ChangeLog | 7 +++++++
>> lib/mountlist.c | 11 ++++++++++-
>> 2 files changed, 17 insertions(+), 1 deletion(-)
>>
>> diff --git a/ChangeLog b/ChangeLog
>> index 4eb5bcb1d..41e284558 100644
>> --- a/ChangeLog
>> +++ b/ChangeLog
>> @@ -1,3 +1,10 @@
>> +2020-10-27 Pádraig Brady <P@draigBrady.com>
>> +
>> + mountlist: recognize more file system types as remote
>> +
>> + * lib/mountlist.c (ME_REMOTE): Sync previously unconsidered
>> + "remote" file systems from stat.c in coreutils.
>> +
>> 2020-10-26 Paul Eggert <eggert@cs.ucla.edu>
>>
>> sys_stat: update comments for S_IRWXUGO, S_IXUGO
>> diff --git a/lib/mountlist.c b/lib/mountlist.c
>> index ca1be63f2..8205c29bd 100644
>> --- a/lib/mountlist.c
>> +++ b/lib/mountlist.c
>> @@ -224,7 +224,7 @@ me_remote (char const *fs_name, char const *fs_type
>> _GL_UNUSED) #ifndef ME_REMOTE
>> /* A file system is "remote" if its Fs_name contains a ':'
>> or if (it is of type (smbfs or cifs) and its Fs_name starts with '//')
>> - or if it is of type (afs or auristorfs)
>> + or if it is of any other of the listed types
>> or Fs_name is equal to "-hosts" (used by autofs to mount remote fs). */
>> # define ME_REMOTE(Fs_name, Fs_type) \
>> (strchr (Fs_name, ':') != NULL \
>> @@ -233,8 +233,17 @@ me_remote (char const *fs_name, char const *fs_type
>> _GL_UNUSED) && (strcmp (Fs_type, "smbfs") == 0 \
>>
>> || strcmp (Fs_type, "smb3") == 0 \
>> || strcmp (Fs_type, "cifs") == 0)) \
>>
>> + || strcmp (Fs_type, "acfs") == 0 \
>>
>> || strcmp (Fs_type, "afs") == 0 \
>>
>> + || strcmp (Fs_type, "coda") == 0 \
>>
>> || strcmp (Fs_type, "auristorfs") == 0 \
>>
>> + || strcmp (Fs_type, "fhgfs") == 0 \
>> + || strcmp (Fs_type, "gpfs") == 0 \
>> + || strcmp (Fs_type, "ibrix") == 0 \
>> + || strcmp (Fs_type, "ocfs2") == 0 \
>> + || strcmp (Fs_type, "prl_fs") == 0 \
>> + || strcmp (Fs_type, "vboxsf") == 0 \
>> + || strcmp (Fs_type, "vxfs") == 0 \
>>
>> || strcmp ("-hosts", Fs_name) == 0)
>>
>> #endif
Thanks for the review.
Upon further consideration I'm reluctant to include
the "VM" file systems here. I.e. vboxsf and prl_fs,
as they do consume space on the local machine.
I'll add a comment about those instead, and will push.
cheers,
Pádraig
prev parent reply other threads:[~2020-11-03 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 21:23 [PATCH] mountlist: recognize more file system types as remote Pádraig Brady
2020-11-03 8:31 ` Kamil Dudka
2020-11-03 14:08 ` Pádraig Brady [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e5f76f1-e958-68d3-db7b-3703ec36b506@draigBrady.com \
--to=p@draigbrady.com \
--cc=bug-gnulib@gnu.org \
--cc=kdudka@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).