Util-Linux package development
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Quentin Rameau <quinq@fifth.space>
Cc: util-linux@vger.kernel.org
Subject: Re: mount: sshfs problem with "defaults" option after 2.39 upgrade
Date: Sun, 21 May 2023 20:58:01 +0200	[thread overview]
Message-ID: <9c4d0dc2-de5b-4e34-9489-01e00a71e2da@t-8ch.de> (raw)
In-Reply-To: <20230521201534.62dadbc8.quinq@fifth.space>

On 2023-05-21 20:15:34+0200, Quentin Rameau wrote:
> > Hi Quentin,
> 
> Hi Thomas,
> 
> > > 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'
> > 
> > Could you try https://github.com/util-linux/util-linux/pull/2250 ?
> 
> This makes that problem go away indeed, thank you!

Great, you're welcome!

> On a side-note, should that flag be applied to other generic parameters
> too, like user(s) for example?

I guess they are useful for the helpers.

If the helpers were able to handle it before it should be fine.
(They were passed in 2.38)

One could even argue that "defaults" should have been fine to be passed,
but now it's a regression so needs to be fixed.

Thomas

  reply	other threads:[~2023-05-21 18:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21 16:18 mount: sshfs problem with "defaults" option after 2.39 upgrade Quentin Rameau
2023-05-21 18:06 ` Thomas Weißschuh
2023-05-21 18:15   ` Quentin Rameau
2023-05-21 18:58     ` Thomas Weißschuh [this message]
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=9c4d0dc2-de5b-4e34-9489-01e00a71e2da@t-8ch.de \
    --to=thomas@t-8ch.de \
    --cc=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