I've just tested this with 2.6.34 and as expected the bug is still there. It would be as this is probably a result of the design of ecryptfs. Should I submit an upstream bug report?
I've just tested this with 2.6.34 and as expected the bug is still there. It would be as this is probably a result of the design of ecryptfs. Should I submit an upstream bug report?