Util-Linux package development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Stanislav Brabec <sbrabec@suse.cz>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] mount: Do not call mnt_pretty_path() on net file systems.
Date: Fri, 22 Feb 2019 11:26:07 +0100	[thread overview]
Message-ID: <20190222102607.y6hfrxjacbpxtru3@ws.net.home> (raw)
In-Reply-To: <05bb1dd3-016d-9166-3e73-29bbc307907c@suse.cz>

On Tue, Feb 19, 2019 at 04:50:26PM +0100, Stanislav Brabec wrote:
> Dne 06. 02. 19 v 11:58 Karel Zak napsal(a):
> > On Wed, Feb 06, 2019 at 12:07:54AM +0100, Stanislav Brabec wrote:
> >>  sys-utils/mount.c | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > Applied, thanks!
> > 
> > Please, send also updates for the mnt_fstype_is_pseudofs().
> > 
> 
> I started to inspect file systems available in SUSE, and I found
> that there is an another category of file systems: File systems that
> have a source (so they are not pseudo file systems), but information
> provided by the kernel is not sufficient to check whether a
> particular source is already mounted.
> 
> Some of them are completely undetectable (both source and FS type
> provide generic information only), some are detectable by source,
> but not by FS type, some are detectable by FS type, but source match
> cannot be used.
> 
> For these file systems, mount(8) cannot guarantee that the correct
> volume is mounted. Only some guesses are possible.

The question is how critical is it for us... maybe all we need is to
document mount(8) limitations for these cases.

> Maybe it should warn about it, or it should refuse such file systems in the fstab.
> 
> 
> Examples of undetectable FUSE file systems:
> 
> xdg-document-portal is completely undetectable; it can be ran once per UID
> /dev/fuse on /run/user/10027/doc type fuse (rw,nosuid,nodev,relatime,user_id=10027,group_id=100)
> 376 536 0:65 / /run/user/10027/doc rw,nosuid,nodev,relatime - fuse /dev/fuse rw,user_id=10027,group_id=100

No subtype ? How FUSE driver redirects it to the right code?

> 
> curlftpfs undetectable by type, detectable by source
> curlftpfs#ftp://ftp.suse.com/ on /home/sbrabec/T type fuse (rw,nosuid,nodev,relatime,user_id=10027,group_id=100)
> 544 510 0:47 / /sys/fs/fuse/connections rw,relatime master:282 - fusectl fusectl rw

 "subtype#" is deprecated; I guess fuse.curlftpfs has to work ;-)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2019-02-22 10:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 22:57 [PATCH] mount: Do not call mnt_pretty_path() on net file systems Stanislav Brabec
2019-02-05 23:07 ` Stanislav Brabec
2019-02-06 10:58   ` Karel Zak
2019-02-19 15:50     ` Stanislav Brabec
2019-02-22 10:26       ` Karel Zak [this message]
2019-02-22 18:39         ` Stanislav Brabec

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=20190222102607.y6hfrxjacbpxtru3@ws.net.home \
    --to=kzak@redhat.com \
    --cc=sbrabec@suse.cz \
    --cc=util-linux@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