From: Martin Steigerwald <Martin@lichtvoll.de>
To: Tyler Hicks <tyhicks@canonical.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: ecryptfs doesn´t like noauto and noatime
Date: Tue, 17 Jan 2012 09:35:31 +0100 [thread overview]
Message-ID: <201201170935.32281.Martin@lichtvoll.de> (raw)
In-Reply-To: <20120117065536.GB4262@boyd>
Am Dienstag, 17. Januar 2012 schrieb Tyler Hicks:
> On 2012-01-16 10:44:21, Martin Steigerwald wrote:
> > Hi!
> >
> > I have
> >
> > merkaba:~> grep ecrypt /etc/fstab
> > /home/.ms /home/ms ecryptfs
> > noatime,noauto 0 0
> >
> > And get:
> >
> > merkaba:~> mount /home/ms
>
> Is this the *exact* mount command that you're running? You're not
> invoking /sbin/mount.ecryptfs directly, using mount -t ecryptfs, or
> anything else?
Yes, this is copied-and-pasted.
> > Passphrase:
> >
> > Attempting to mount with the following options:
> > ecryptfs_unlink_sigs
> > ecryptfs_fnek_sig=0408d19ec184c207
> > ecryptfs_key_bytes=32
> > ecryptfs_cipher=aes
> > ecryptfs_sig=0408d19ec184c207
> >
> > Error mounting eCryptfs: [-5] Input/output error
> > Check your system logs; visit <http://launchpad.net/ecryptfs>
> >
> >
> > Still it works.
> >
> >
> > In dmesg I see:
> >
> > [ 2657.888355] ecryptfs_parse_options: eCryptfs: unrecognized option
> > [noauto]
> > [ 2657.888359] ecryptfs_parse_options: eCryptfs: unrecognized option
> > [noatime]
>
> Neither of these options should be making their way to the kernel in
> the string form. noauto is consumed by the mount utility and should be
> stripped out entirely before constructing the final mount options
> string for the kernel. noatime should be stripped out and converted
> into a mountflags bit (see man 2 mount).
>
> It looks like ecryptfs_generate_mount_flags() is incomplete since it
> forgets to handle some options (at least noatime and noauto). I created
> bug #917509 to track this:
>
> https://launchpad.net/bugs/917509
Thanks.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
prev parent reply other threads:[~2012-01-17 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 9:44 ecryptfs doesn´t like noauto and noatime Martin Steigerwald
2012-01-17 1:07 ` Jakob Unterwurzacher
2012-01-17 8:37 ` Martin Steigerwald
2012-01-17 9:46 ` Jakob Unterwurzacher
2012-01-30 10:58 ` Martin Steigerwald
2012-01-30 18:49 ` Dustin Kirkland
2012-01-17 6:55 ` Tyler Hicks
2012-01-17 8:35 ` Martin Steigerwald [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201201170935.32281.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=ecryptfs@vger.kernel.org \
--cc=tyhicks@canonical.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