ecryptfs: Could not parse tag 70 packet from filename
Bug #357345 reported by
Dustin Kirkland
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Fix Released
|
Medium
|
Tyler Hicks | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Medium
|
Tim Gardner |
Bug Description
My dmesg is flooded with these on an up-to-date jaunty kernel.
[ 45.653441] ecryptfs_
[ 45.653444] ecryptfs_
This was initially reported in Bug #331082. I'm opening here because it's a separate issue.
Looking at the underlying data, I cannot find any non-encrypted filenames.
Furthermore, I don't see any encrypted filenames in my cleartext mountpoint.
Please let me know how I can help debug this issue, Tyler.
:-Dustin
Changed in linux (Ubuntu): | |
assignee: | nobody → tyhicks |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in ecryptfs: | |
assignee: | nobody → tyhicks |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | Confirmed → In Progress |
summary: |
- Could not parse tag 70 packet from filename + ecryptfs: Could not parse tag 70 packet from filename |
To post a comment you must log in.
Please apply this patch, reproduce and let me know what filename(s) are causing this issue.