Comment 3 for bug 782646

There is no security hole here. The only thing that ureadahead does is call readahead() on certain files to tell the kernel to cache these files for later use. I'm not certain how ecryptfs works, but I'm fairly certain there's no security weakness here. For instance, it's likely that ureadahead reads the encrypted information in to memory for later decryption when you log in or something.