Messages in this thread | | | From | Sasha Levin <> | Date | Fri, 22 Jun 2012 19:47:35 +0200 | Subject | Re: [PATCH 1/3] eCryptfs: Gracefully refuse miscdev file ops on inherited/passed files |
| |
On Wed, Jun 13, 2012 at 2:05 AM, Tyler Hicks <tyhicks@canonical.com> wrote: > File operations on /dev/ecryptfs would BUG() when the operations were > performed by processes other than the process that originally opened the > file. This could happen with open files inherited after fork() or file > descriptors passed through IPC mechanisms. Rather than calling BUG(), an > error code can be safely returned in most situations. > > In ecryptfs_miscdev_release(), eCryptfs still needs to handle the > release even if the last file reference is being held by a process that > didn't originally open the file. ecryptfs_find_daemon_by_euid() will not > be successful, so a pointer to the daemon is stored in the file's > private_data. The private_data pointer is initialized when the miscdev > file is opened and only used when the file is released. > > https://launchpad.net/bugs/994247 > > Signed-off-by: Tyler Hicks <tyhicks@canonical.com> > Reported-by: Sasha Levin <levinsasha928@gmail.com> > Cc: Sasha Levin <levinsasha928@gmail.com> > ---
I've been running it a while now and haven't seen the problem I've reported reproducing.
Is it possible to merge this fix into 3.5?
| |