From: Tyler Hicks <tyhicks@canonical.com>
To: Richard Weinberger <richard@nod.at>
Cc: ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
Date: Mon, 3 Aug 2015 18:07:54 -0500 [thread overview]
Message-ID: <20150803230754.GB2342@boyd> (raw)
In-Reply-To: <55BFB39D.5070702@nod.at>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On 2015-08-03 20:31:57, Richard Weinberger wrote:
> Tyler,
>
> Am 03.08.2015 um 07:27 schrieb Tyler Hicks:
> >> So ecryptfs definitely supports mounting the same lower path multiple times?
> >> What is the benefit of that behavior?
> >
> > No, it doesn't support that in a way that provides consistency among all
> > of the eCryptfs mounts.
>
> Okay, then I'd argument to give my patch a try although it is not the solution
> to the problem I've reported. :-)
> If you don't mind I'll resend with a proper changelog.
That patch isn't correct since it assumes that all eCryptfs super blocks
are equal if the lower paths (and, ultimately, the lower inode) are
equal. However, the lower path is only one of many properties of an
eCryptfs superblock. For example, the second mount may have been
configured to use a different file encryption key.
Tyler
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-03 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438338190-22518-1-git-send-email-richard@nod.at>
[not found] ` <20150802010259.GA19522@boyd>
2015-08-02 7:51 ` [RFC][PATCH] ecryptfs: Allow only one instance per lower path Richard Weinberger
2015-08-03 5:27 ` Tyler Hicks
2015-08-03 18:31 ` Richard Weinberger
2015-08-03 23:07 ` Tyler Hicks [this message]
2015-08-04 5:46 ` Richard Weinberger
2015-08-04 14:52 ` Tyler Hicks
2015-08-05 22:02 ` [PATCH] eCryptfs: Invalidate dcache entries when lower i_nlink is zero Tyler Hicks
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=20150803230754.GB2342@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).