Bug 1374945

Summary:	Broken Subdirs in ecryptfs directory with kernel 4.7.2
Product:	[Fedora] Fedora	Reporter:	marc-schmitzer
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone:	---	Flags:	jforbes: needinfo?
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-28 17:16:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description marc-schmitzer 2016-09-10 20:04:20 UTC

Description of problem:

I have ~/Private set up encrypted with ecryptfs. With the 4.7.2 Fedora kernel, some of the subdirectories in that directory appear broken when it is mounted.

There are two symptoms:
  * Some directories appear in the directory listing, but stat on them returns ENOENT. This happens even with simple, ascii-only directory names.
  * Some non-ascii characters in directory names appear incorrectly.

Booting the 4.6.7 kernel shows the directory completely intact.

Version-Release number of selected component (if applicable):

  * kernel-PAE-4.7.2-201.fc24.i686
  * ecryptfs-utils-111-1.fc24.i686

How reproducible:

Always

Steps to Reproduce:
1. Boot kernel 4.7.2 with encrypted ~/Private configured

Actual results:
Broken directories in ~/Private

Comment 1 marc-schmitzer 2016-09-10 20:52:34 UTC

Forgot to mention: Filename encryption is active.

Comment 2 marc-schmitzer 2016-09-17 20:15:37 UTC

The 4.7.3 kernel has the same problem.

I re-created the private dir under the 4.7.3 kernel and it seems to work now.

Comment 3 Justin M. Forbes 2017-04-11 14:43:45 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 4 Justin M. Forbes 2017-04-28 17:16:53 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.