From: Carlos Llamas <cmllamas@google.com>
To: Li Li <dualli@chromium.org>
Cc: dualli@google.com, corbet@lwn.net, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
donald.hunter@gmail.com, gregkh@linuxfoundation.org,
arve@android.com, tkjos@android.com, maco@android.com,
joel@joelfernandes.org, brauner@kernel.org, surenb@google.com,
arnd@arndb.de, masahiroy@kernel.org, bagasdotme@gmail.com,
horms@kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
hridya@google.com, smoreland@google.com, kernel-team@android.com
Subject: Re: [PATCH net-next v10 1/2] binderfs: add new binder devices to binder_devices
Date: Mon, 16 Dec 2024 18:01:24 +0000 [thread overview]
Message-ID: <Z2Bq9CjXO6FXIFjl@google.com> (raw)
In-Reply-To: <20241212224114.888373-2-dualli@chromium.org>
On Thu, Dec 12, 2024 at 02:41:13PM -0800, Li Li wrote:
> From: Li Li <dualli@google.com>
>
> When binderfs is not enabled, the binder driver parses the kernel
> config to create all binder devices. All of the new binder devices
> are stored in the list binder_devices.
>
> When binderfs is enabled, the binder driver creates new binder devices
> dynamically when userspace applications call BINDER_CTL_ADD ioctl. But
> the devices created in this way are not stored in the same list.
>
> This patch fixes that.
>
> Signed-off-by: Li Li <dualli@google.com>
> ---
> drivers/android/binder.c | 5 +++++
> drivers/android/binder_internal.h | 8 ++++++++
> drivers/android/binderfs.c | 2 ++
> 3 files changed, 15 insertions(+)
>
> diff --git a/drivers/android/binder.c b/drivers/android/binder.c
> index ef353ca13c35..0a16acd29653 100644
> --- a/drivers/android/binder.c
> +++ b/drivers/android/binder.c
> @@ -6928,6 +6928,11 @@ const struct binder_debugfs_entry binder_debugfs_entries[] = {
> {} /* terminator */
> };
>
> +void binder_add_device(struct binder_device *device)
> +{
> + hlist_add_head(&device->hlist, &binder_devices);
> +}
> +
> static int __init init_binder_device(const char *name)
> {
> int ret;
> diff --git a/drivers/android/binder_internal.h b/drivers/android/binder_internal.h
nit: I believe you the following hunk should be in this patch no?
/**
* struct binder_device - information about a binder device node
- * @hlist: list of binder devices (only used for devices requested via
- * CONFIG_ANDROID_BINDER_DEVICES)
+ * @hlist: list of binder devices
* @miscdev: information about a binder character device node
* @context: binder context information
* @binderfs_inode: This is the inode of the root dentry of the super block
> index f8d6be682f23..1f21ad3963b1 100644
> --- a/drivers/android/binder_internal.h
> +++ b/drivers/android/binder_internal.h
> @@ -582,4 +582,12 @@ struct binder_object {
> };
> };
>
> +/**
> + * Add a binder device to binder_devices
> + * @device: the new binder device to add to the global list
> + *
> + * Not reentrant as the list is not protected by any locks
> + */
> +void binder_add_device(struct binder_device *device);
> +
> #endif /* _LINUX_BINDER_INTERNAL_H */
> diff --git a/drivers/android/binderfs.c b/drivers/android/binderfs.c
> index ad1fa7abc323..bc6bae76ccaf 100644
> --- a/drivers/android/binderfs.c
> +++ b/drivers/android/binderfs.c
> @@ -207,6 +207,8 @@ static int binderfs_binder_device_create(struct inode *ref_inode,
> fsnotify_create(root->d_inode, dentry);
> inode_unlock(d_inode(root));
>
> + binder_add_device(device);
> +
> return 0;
>
> err:
> --
> 2.47.1.613.gc27f4b7a9f-goog
>
Other than the comment above it LGTM. Feel free to add:
Acked-by: Carlos Llamas <cmllamas@google.com>
next prev parent reply other threads:[~2024-12-16 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 22:41 [PATCH net-next v10 0/2] binder: report txn errors via generic netlink Li Li
2024-12-12 22:41 ` [PATCH net-next v10 1/2] binderfs: add new binder devices to binder_devices Li Li
2024-12-15 22:27 ` Jakub Kicinski
2024-12-16 5:06 ` Li Li
2024-12-16 18:01 ` Carlos Llamas [this message]
2024-12-12 22:41 ` [PATCH net-next v10 2/2] binder: report txn errors via generic netlink Li Li
2024-12-16 18:12 ` Carlos Llamas
2024-12-16 18:58 ` Li Li
2024-12-17 1:41 ` Jakub Kicinski
2024-12-17 3:53 ` Li Li
2024-12-17 14:51 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z2Bq9CjXO6FXIFjl@google.com \
--to=cmllamas@google.com \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dualli@chromium.org \
--cc=dualli@google.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=hridya@google.com \
--cc=joel@joelfernandes.org \
--cc=kernel-team@android.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=smoreland@google.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).