Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names

2018-03-28 Thread Tyler Hicks
On 03/28/2018 08:33 AM, Guenter Roeck wrote: > On 03/27/2018 08:58 AM, Tyler Hicks wrote: >> Hello Guenter >> >> On 02/13/2018 04:36 PM, Guenter Roeck wrote: >>> Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or >>> plaintext name") was supposed to fix a situation where two

Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names

2018-03-28 Thread Tyler Hicks
On 03/28/2018 08:33 AM, Guenter Roeck wrote: > On 03/27/2018 08:58 AM, Tyler Hicks wrote: >> Hello Guenter >> >> On 02/13/2018 04:36 PM, Guenter Roeck wrote: >>> Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or >>> plaintext name") was supposed to fix a situation where two

Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names

2018-03-28 Thread Guenter Roeck
On 03/27/2018 08:58 AM, Tyler Hicks wrote: Hello Guenter On 02/13/2018 04:36 PM, Guenter Roeck wrote: Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or plaintext name") was supposed to fix a situation where two files with the same name and same inode could be created in

Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names

2018-03-28 Thread Guenter Roeck
On 03/27/2018 08:58 AM, Tyler Hicks wrote: Hello Guenter On 02/13/2018 04:36 PM, Guenter Roeck wrote: Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or plaintext name") was supposed to fix a situation where two files with the same name and same inode could be created in

Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names

2018-03-27 Thread Tyler Hicks
Hello Guenter On 02/13/2018 04:36 PM, Guenter Roeck wrote: > Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or > plaintext name") was supposed to fix a situation where two files with > the same name and same inode could be created in ecryptfs. One of those > files had an

Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names

2018-03-27 Thread Tyler Hicks
Hello Guenter On 02/13/2018 04:36 PM, Guenter Roeck wrote: > Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or > plaintext name") was supposed to fix a situation where two files with > the same name and same inode could be created in ecryptfs. One of those > files had an

Re: ecryptfs: Restore support for both encrypted and unencrypted file names

2018-02-28 Thread Guenter Roeck
ping On Tue, Feb 13, 2018 at 02:36:08PM -0800, Guenter Roeck wrote: > Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or > plaintext name") was supposed to fix a situation where two files with > the same name and same inode could be created in ecryptfs. One of those > files had

Re: ecryptfs: Restore support for both encrypted and unencrypted file names

2018-02-28 Thread Guenter Roeck
ping On Tue, Feb 13, 2018 at 02:36:08PM -0800, Guenter Roeck wrote: > Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or > plaintext name") was supposed to fix a situation where two files with > the same name and same inode could be created in ecryptfs. One of those > files had

[PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names

2018-02-13 Thread Guenter Roeck
Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or plaintext name") was supposed to fix a situation where two files with the same name and same inode could be created in ecryptfs. One of those files had an encrypted file name, the other file name was unencrypted. After commit

[PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names

2018-02-13 Thread Guenter Roeck
Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or plaintext name") was supposed to fix a situation where two files with the same name and same inode could be created in ecryptfs. One of those files had an encrypted file name, the other file name was unencrypted. After commit