From: Jakub Kicinski <kuba@kernel•org>
To: Li Li <dualli@chromium•org>
Cc: dualli@google•com, corbet@lwn•net, gregkh@linuxfoundation•org,
arve@android•com, tkjos@android•com, maco@android•com,
joel@joelfernandes•org, brauner@kernel•org, cmllamas@google•com,
surenb@google•com, arnd@arndb•de, masahiroy@kernel•org,
devel@driverdev•osuosl.org, linux-kernel@vger•kernel.org,
netdev@vger•kernel.org, hridya@google•com, smoreland@google•com,
kernel-team@android•com, Donald Hunter <donald.hunter@gmail•com>
Subject: Re: [PATCH v2 1/1] binder: report txn errors via generic netlink
Date: Fri, 11 Oct 2024 09:09:41 -0700 [thread overview]
Message-ID: <20241011090941.3494f1ef@kernel.org> (raw)
In-Reply-To: <20241011064427.1565287-2-dualli@chromium.org>
On Thu, 10 Oct 2024 23:44:27 -0700 Li Li wrote:
> Frozen tasks can't process binder transactions, so sync binder
> transactions will fail with BR_FROZEN_REPLY and async binder
> transactions will be queued in the kernel async binder buffer.
> As these queued async transactions accumulates over time, the async
> buffer will eventually be running out, denying all new transactions
> after that with BR_FAILED_REPLY.
>
> In addition to the above cases, different kinds of binder error codes
> might be returned to the sender. However, the core Linux, or Android,
> system administration process never knows what's actually happening.
>
> This patch introduces the Linux generic netlink messages into the binder
> driver so that the Linux/Android system administration process can
> listen to important events and take corresponding actions, like stopping
> a broken app from attacking the OS by sending huge amount of spamming
> binder transactions.
>
> To prevent making the already bloated binder.c even bigger, a new source
> file binder_genl.c is created to host those generic netlink code.
Please add a YNL spec for the new family, and use it to codegen
the basics like policy and op tables:
https://docs.kernel.org/next/userspace-api/netlink/specs.html
Don't hesitate to ask if you have any questions.
prev parent reply other threads:[~2024-10-11 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 6:44 [PATCH v2 0/1] binder: report txn errors via generic netlink (genl) Li Li
2024-10-11 6:44 ` [PATCH v2 1/1] binder: report txn errors via generic netlink Li Li
2024-10-11 6:51 ` Greg KH
2024-10-11 7:42 ` Li Li
2024-10-11 16:09 ` Jakub Kicinski [this message]
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=20241011090941.3494f1ef@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=arve@android$(echo .)com \
--cc=brauner@kernel$(echo .)org \
--cc=cmllamas@google$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=devel@driverdev$(echo .)osuosl.org \
--cc=donald.hunter@gmail$(echo .)com \
--cc=dualli@chromium$(echo .)org \
--cc=dualli@google$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=hridya@google$(echo .)com \
--cc=joel@joelfernandes$(echo .)org \
--cc=kernel-team@android$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=maco@android$(echo .)com \
--cc=masahiroy@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=smoreland@google$(echo .)com \
--cc=surenb@google$(echo .)com \
--cc=tkjos@android$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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