On 02/15/2012 12:04 PM, Colin King wrote:

From: Colin Ian King<colin.king@canonical.com>

SRU Justification:

Stacking ecryptfs over ecryptfs can lead to many kinds of errors.
There doesn't seem to be any good usecase for this and we should
follow the upstream policy of disallowing the configuration.

Fix: Without the fix, we can stack ecryptfs over ecryptfs which can
lead to all sorts of trouble. With the fix, mount fails with EINVAL
and the kernel reports:

"Mount on filesystem of the type eCryptfs explicitly disasslowed due
to known incompatibilities"

This is a backport of commit 4403158ba295c8e36f6736b1bb12d0f7e1923dac

https://bugs.launchpad.net/ubuntu/+bug/932987

Colin Ian King (1):
Ban ecryptfs over ecryptfs

fs/ecryptfs/main.c | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)





--
Tim Gardner tim.gardner@canonical.com

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team

On 02/15/2012 11:04 AM, Colin King wrote:

From: Colin Ian King<colin.king@canonical.com>

SRU Justification:

Stacking ecryptfs over ecryptfs can lead to many kinds of errors.
There doesn't seem to be any good usecase for this and we should
follow the upstream policy of disallowing the configuration.

Fix: Without the fix, we can stack ecryptfs over ecryptfs which can
lead to all sorts of trouble. With the fix, mount fails with EINVAL
and the kernel reports:

"Mount on filesystem of the type eCryptfs explicitly disasslowed due
to known incompatibilities"

This is a backport of commit 4403158ba295c8e36f6736b1bb12d0f7e1923dac

https://bugs.launchpad.net/ubuntu/+bug/932987

Colin Ian King (1):
Ban ecryptfs over ecryptfs

fs/ecryptfs/main.c | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)





--
Brad Figg brad.figg@canonical.com http://www.canonical.com

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team