Util-Linux package development
 help / color / mirror / Atom feed
From: Andreas Henriksson <andreas@fatal.se>
To: Anthony DeRobertis <anthony@derobert.net>, 801527@bugs.debian.org
Cc: util-linux@vger.kernel.org
Subject: Re: Bug#801527: mount believes correctly-formatted UDF uid=forget option is in error
Date: Sun, 11 Oct 2015 22:58:48 +0200	[thread overview]
Message-ID: <20151011205848.GA16027@fatal.se> (raw)
In-Reply-To: <20151011172712.28932.10676.reportbug@Watt.home>

Control: tags -1 + upstream

Hello Anthony DeRobertis.

Thanks for your bug report.

On Sun, Oct 11, 2015 at 01:27:12PM -0400, Anthony DeRobertis wrote:
> Package: mount
> Version: 2.27-3
> Severity: important
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I recently upgraded a system to Jessie (from Wheezy), and mounting UDF
> filesystems broke. I confirmed the bug still exists on the machine I'm
> reporting from (which runs testing/unstable).

Jessie and onwards uses a new mount implementation based on libmount.

> 
> It appears mount has decided that "uid=ignore", "uid=forget",
> "gid=ignore", and "gid=forget" are invalid mount options. Instead of
> passing them to the kernel as it used to, it now prints "mount: failed
> to parse mount options"

Using LIBMOUNT_DEBUG=all mount -t udf -o uid=ignore,gid=forget ...
shows the following message (among others):

24171: libmount:    UTILS: cannot convert 'ignore' username to UID

... and according to the following code you seem to be very right
that except an actual uid you can also pass 'uid=ignore' or
'uid=forget' explicitly:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/fs/udf/super.c#n352

I see several possible options for implementing this in the future:
 - special-case 'ignore' and 'forget' and pass those as is.
 - if uid-lookup fails, try the above.
 - (assuming different filesystems have different special options)
   let any fs-option through as-is if 'smart lookup' fails.
 - ...

I'm adding the upstream mailing list to CC in the hope that someone
has a suggestion on how to best handle this case.


> 
> busybox mount works fine, so the kernel is still happy with the options.
> And even in 4.2, they're still documented in
> Documentation/filesystems/udf.txt, so they should work.

Thanks for the extra data point.


Regards,
Andreas Henriksson

       reply	other threads:[~2015-10-11 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151011172712.28932.10676.reportbug@Watt.home>
2015-10-11 20:58 ` Andreas Henriksson [this message]
2015-10-12 10:00   ` Bug#801527: mount believes correctly-formatted UDF uid=forget option is in error Karel Zak

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=20151011205848.GA16027@fatal.se \
    --to=andreas@fatal.se \
    --cc=801527@bugs.debian.org \
    --cc=anthony@derobert.net \
    --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