From: Quentin Rameau <quinq@fifth.space>
To: util-linux@vger.kernel.org
Subject: mount: sshfs problem with "defaults" option after 2.39 upgrade
Date: Sun, 21 May 2023 18:18:14 +0200 [thread overview]
Message-ID: <20230521181814.0b0f2d38.quinq@fifth.space> (raw)
Hi,
I just updated util-linux to 2.39 from 2.38.1 (on Alpine Linux),
and new mount triggers an error for an old sshfs fstab mount entry,
that was working until now.
The line in question is:
user@host:path /media/ssh/path sshfs defaults,nosuid,nodev,noexec,noatime,noauto,_netdev,user,idmap=user,allow_other,rec 0 0
and fails with:
$ mount /media/ssh/path
fuse: unknown option(s): `-o defaults'
I can see in the trace that "defaults" is actually passed to the helper
30906 execve("/sbin/mount.sshfs", ["/sbin/mount.sshfs", "user@host:path", "/media/ssh/path", "-o", "rw,defaults,noatime,_netdev,...", <truncated here>
And running it with LIBMOUNT_DEBUG=all shows
30933: libmount: UPDATE: 30933: libmount: FS: synced: vfs: 'rw,noatime,nodev,nosuid,noexec' fs: 'idmap=user,allow_other,reconnect' user: 'defaults,noauto,_netdev,, optstr: 'rw,defaults,noatime,noauto,_netdev,user=quinq,nodev,nosuid,noexec,allow_other,reconnect'
[...]
optstr: rw,defaults,noatime,noauto,_netdev,nodev,nosuid,noexec,idmap=user,allow_other,reconnect
VFS-optstr: rw,noatime,nodev,nosuid,noexec
FS-opstr: idmap=user,allow_other,reconnect
user-optstr: defaults,noauto,_netdev
The "defaults" option is stripped from the analog traces with mount 2.38.1
next reply other threads:[~2023-05-21 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 16:18 Quentin Rameau [this message]
2023-05-21 18:06 ` mount: sshfs problem with "defaults" option after 2.39 upgrade Thomas Weißschuh
2023-05-21 18:15 ` Quentin Rameau
2023-05-21 18:58 ` Thomas Weißschuh
2023-05-21 19:20 ` Quentin Rameau
2023-05-22 6:55 ` Thomas Weißschuh
2023-05-22 16:56 ` Quentin Rameau
2023-05-22 14:21 ` Karel Zak
2023-05-22 15:33 ` Karel Zak
2023-05-22 16:55 ` Quentin Rameau
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=20230521181814.0b0f2d38.quinq@fifth.space \
--to=quinq@fifth.space \
--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