This bug report is all over the place. I posted a fix for bug #509180 in that bug report and pieces of this bug report do seem related.
I'm not sure I like loops to handle -EINTR in kernel code. That's normally for user space to handle and I don't see why this is any different. I may consider one retry after an -EINTR error from vfs_read(), but not a loop. I'm fairly confident that the fix I posted in bug #509180 will solve the issues that the -EINTR patch aims to address. Let me know if anyone feels differently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/521523 Title: severe ecryptfs corruption -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
