From: Alice Ryhl <aliceryhl@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, cmllamas@google.com,
surenb@google.com, omosnace@redhat.com, shuah@kernel.org,
arnd@arndb.de, masahiroy@kernel.org, bagasdotme@gmail.com,
horms@kernel.org, tweek@google.com, paul@paul-moore.com,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
netdev@vger.kernel.org, selinux@vger.kernel.org,
hridya@google.com, smoreland@google.com, ynaffit@google.com,
kernel-team@android.com
Subject: Re: [PATCH v17 0/3] binder: report txn errors via generic netlink
Date: Wed, 16 Apr 2025 10:41:54 +0000 [thread overview]
Message-ID: <Z_-Jcv-GN68zILvH@google.com> (raw)
In-Reply-To: <20250415071017.3261009-1-dualli@chromium.org>
On Tue, Apr 15, 2025 at 12:10:14AM -0700, Li Li wrote:
> From: Li Li <dualli@google.com>
>
> It's a known issue that neither the frozen processes nor the system
> administration process of the OS can correctly deal with failed binder
> transactions. The reason is that there's no reliable way for the user
> space administration process to fetch the binder errors from the kernel
> binder driver.
>
> Android is such an OS suffering from this issue. Since cgroup freezer
> was used to freeze user applications to save battery, innocent frozen
> apps have to be killed when they receive sync binder transactions or
> when their async binder buffer is running out.
>
> 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 transactiions.
I'm a bit confused about this series. Why is [PATCH] binder: add
setup_report permission a reply to [PATCH v17 1/3] lsm, selinux: Add
setup_report permission to binder? Which patches are supposed to be
included and in which order?
Alice
next prev parent reply other threads:[~2025-04-16 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 7:10 [PATCH v17 0/3] binder: report txn errors via generic netlink Li Li
2025-04-15 7:10 ` [PATCH v17 1/3] lsm, selinux: Add setup_report permission to binder Li Li
2025-04-15 7:13 ` [PATCH] binder: add setup_report permission Li Li
2025-04-15 7:16 ` [PATCH 1/2] policy,tests: add test for new permission binder:setup_report Li Li
2025-04-15 7:47 ` [PATCH v2] " Li Li
2025-04-15 16:13 ` [PATCH v17 1/3] lsm, selinux: Add setup_report permission to binder Casey Schaufler
2025-04-16 16:00 ` Li Li
2025-04-16 22:58 ` Casey Schaufler
2025-04-15 7:10 ` [PATCH v17 2/3] binder: report txn errors via generic netlink Li Li
2025-04-15 7:10 ` [PATCH v17 3/3] binder: transaction report binder_features flag Li Li
2025-04-16 10:41 ` Alice Ryhl [this message]
2025-04-16 15:57 ` [PATCH v17 0/3] binder: report txn errors via generic netlink Li Li
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=Z_-Jcv-GN68zILvH@google.com \
--to=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--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=omosnace@redhat.com \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=smoreland@google.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=tweek@google.com \
--cc=ynaffit@google.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).