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

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 file

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

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 ecry

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

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 encryp

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

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 88