From: Hang Lu <hangl@codeaurora.org>
To: tkjos@google.com, gregkh@linuxfoundation.org
Cc: tkjos@android.com, maco@android.com, arve@android.com,
joel@joelfernandes.org, christian@brauner.io, hridya@google.com,
surenb@google.com, rdunlap@infradead.org,
linux-kernel@vger.kernel.org, Hang Lu <hangl@codeaurora.org>
Subject: [PATCH 0/2] binder: tell userspace to dump current backtrace when detected oneway spamming
Date: Fri, 9 Apr 2021 17:40:44 +0800 [thread overview]
Message-ID: <1617961246-4502-1-git-send-email-hangl@codeaurora.org> (raw)
Add feature for binder oneway spamming detection, which tells userspace
to dump current backtrace. Fix the missing "BR_FROZEN_REPLY" issue first,
then features.
Hang Lu (2):
binder: fix the missing BR_FROZEN_REPLY in binder_return_strings
binder: tell userspace to dump current backtrace when detected oneway
spamming
drivers/android/binder.c | 30 ++++++++++++++++++++++++++----
drivers/android/binder_alloc.c | 15 ++++++++++++---
drivers/android/binder_alloc.h | 8 +++++++-
drivers/android/binder_internal.h | 6 +++++-
include/uapi/linux/android/binder.h | 8 ++++++++
5 files changed, 58 insertions(+), 9 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2021-04-09 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 9:40 Hang Lu [this message]
2021-04-09 9:40 ` [PATCH 1/2] binder: fix the missing BR_FROZEN_REPLY in binder_return_strings Hang Lu
2021-04-09 15:12 ` Todd Kjos
2021-04-09 9:40 ` [PATCH 2/2] binder: tell userspace to dump current backtrace when detected oneway spamming Hang Lu
2021-04-09 15:16 ` Todd Kjos
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=1617961246-4502-1-git-send-email-hangl@codeaurora.org \
--to=hangl@codeaurora.org \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=gregkh@linuxfoundation.org \
--cc=hridya@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=rdunlap@infradead.org \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=tkjos@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).