diff options
author | Al Viro <viro@zeniv.linux.org.uk> | 2012-08-15 21:06:33 -0400 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2012-09-26 21:08:55 -0400 |
commit | f869e8a7f753e3fd43d6483e796774776f645edb (patch) | |
tree | 3b215f30a040812eb7488bd4596a5c3ae0b50e51 /fs/file_table.c | |
parent | 56007cae94f349387c088e738c7dcb6bc513063b (diff) | |
download | op-kernel-dev-f869e8a7f753e3fd43d6483e796774776f645edb.zip op-kernel-dev-f869e8a7f753e3fd43d6483e796774776f645edb.tar.gz |
expose a low-level variant of fd_install() for binder
Similar situation to that of __alloc_fd(); do not use unless you
really have to. You should not touch any descriptor table other
than your own; it's a sure sign of a really bad API design.
As with __alloc_fd(), you *must* use a first-class reference to
struct files_struct; something obtained by get_files_struct(some task)
(let alone direct task->files) will not do. It must be either
current->files, or obtained by get_files_struct(current) by the
owner of that sucker and given to you.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/file_table.c')
0 files changed, 0 insertions, 0 deletions