From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f66.google.com ([74.125.82.66]:34270 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726843AbeG3QNJ (ORCPT ); Mon, 30 Jul 2018 12:13:09 -0400 From: Christian Brauner To: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Cc: arve@android.com, tkjos@android.com, maco@android.com, rlove@google.com, ben@decadent.org.uk, Christian Brauner Subject: [RFC PATCH 0/4] file: export functions for binder module Date: Mon, 30 Jul 2018 16:37:06 +0200 Message-Id: <20180730143710.14413-1-christian@brauner.io> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hey, We currently plan on turning the Android binder and ashmem driver into a module. We have seen more and more requests by users to be able to use the binder and ashmem features without wanting to convince each distro to enable it by default in their kernel. Debian already started to carry patches for turning them into modules. The main problem is that binder currently uses multiple functions that are not exported and are pretty low-level. The most obvious ones that fall into this category are __alloc_fd(), __fd_install(), get_files_struct(), and put_files_struct(). Being an IPC mechanism binder seems like a reasonable user of these functions. I don't expect this patch to be mergeable but rather to kick-off a discussion if we can either simply export them as they are or how we can get supportable exports that allow access to struct files_struct. Thanks! Christian Christian Brauner (4): file: export __alloc_fd() file: export __fd_install() file: export get_files_struct() file: export put_files_struct() fs/file.c | 4 ++++ 1 file changed, 4 insertions(+) -- 2.17.1