From: Richard Weinberger <richard@nod.at>
To: Tyler Hicks <tyhicks@canonical.com>
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 20:31:57 +0200 [thread overview]
Message-ID: <55BFB39D.5070702@nod.at> (raw)
In-Reply-To: <20150803052758.GA24915@boyd>
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.
> However, multiple mounts on the same lower path is not the cause of this
> bug. The real issue is a stale dcache entry when the lower filesystem
> has been modified without eCryptfs' knowing. I can trigger the same
> warnings with only a single eCryptfs mount.
Interesting, that renders the whole issue into a user triggerable kernel
bug. :-(
Thanks,
//richard
next prev parent reply other threads:[~2015-08-03 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 10:23 [RFC][PATCH] ecryptfs: Allow only one instance per lower path Richard Weinberger
2015-08-02 1:03 ` Tyler Hicks
2015-08-02 7:51 ` Richard Weinberger
2015-08-03 5:27 ` Tyler Hicks
2015-08-03 18:31 ` Richard Weinberger [this message]
2015-08-03 23:07 ` Tyler Hicks
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=55BFB39D.5070702@nod.at \
--to=richard@nod.at \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).