From: Carlos Llamas <cmllamas@google.com>
To: Frode Isaksen <fisaksen@baylibre.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <brauner@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Frode Isaksen" <frode@meta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binder: do not crash on bad transaction in binder_thread_release()
Date: Tue, 1 Apr 2025 03:03:34 +0000 [thread overview]
Message-ID: <Z-tXhrdTtV5t_P5p@google.com> (raw)
In-Reply-To: <20250331152515.113421-1-fisaksen@baylibre.com>
On Mon, Mar 31, 2025 at 05:24:14PM +0200, Frode Isaksen wrote:
> From: Frode Isaksen <frode@meta.com>
>
> Instead of calling BUG(), set the binder_thread to NULL,
Yeap, not crashing the kernel is a good idea.
> as is done in other parts of the code.
> Log if it is a bad transaction (other than in or out).
> The BUG in binder_thread_release() was preceded by
> these warning logs:
> binder: 1198:1217 got reply transaction with bad transaction stack,
> transaction 49693 has target 1198:0
So tid 1217 is sending a reply to an incoming sync transaction. However,
its transaction_stack shows that t->to_thread is NULL. I have no idea
how can this be possible. When the transaction was picked up by 1217,
its info was recorded in its transaction_stack as such:
if (cmd != BR_REPLY && !(t->flags & TF_ONE_WAY)) {
binder_inner_proc_lock(thread->proc);
t->to_parent = thread->transaction_stack;
t->to_thread = thread; <----- HERE
thread->transaction_stack = t;
binder_inner_proc_unlock(thread->proc);
}
I don't understand how 't->to_thread' later becomes NULL, maybe memory
corruption?
> binder: 1198:1217 transaction failed 29201/-71, size 4-0 line 3065
> ...
> binder: release 954:1333 transaction 49693 out, still active
> ...
> binder: release 1198:1217 transaction 49693 out, still active
> kernel BUG at drivers/android/binder.c:5070!
>
> Signed-off-by: Frode Isaksen <frode@meta.com>
> ---
> This bug was discovered, tested and fixed (no more crashes seen) on Meta Quest 3 device.
Do you have a way to reproduce this? It sounds like there is something
else going wrong before and we probably want to fix that.
>
> drivers/android/binder.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/android/binder.c b/drivers/android/binder.c
> index 76052006bd87..c21d7806e42b 100644
> --- a/drivers/android/binder.c
> +++ b/drivers/android/binder.c
> @@ -5302,7 +5302,8 @@ static int binder_thread_release(struct binder_proc *proc,
> "release %d:%d transaction %d %s, still active\n",
> proc->pid, thread->pid,
> t->debug_id,
> - (t->to_thread == thread) ? "in" : "out");
> + (t->to_thread == thread) ? "in" :
> + (t->from == thread) ? "out" : "bad");
>
> if (t->to_thread == thread) {
> thread->proc->outstanding_txns--;
> @@ -5317,7 +5318,7 @@ static int binder_thread_release(struct binder_proc *proc,
> t->from = NULL;
> t = t->from_parent;
> } else
> - BUG();
> + t = NULL;
Dropping BUG() is nice but this could use en error message.
> spin_unlock(&last_t->lock);
> if (t)
> spin_lock(&t->lock);
> --
> 2.49.0
>
Regards,
--
Carlos Llamas
next prev parent reply other threads:[~2025-04-01 3:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 15:24 [PATCH] binder: do not crash on bad transaction in binder_thread_release() Frode Isaksen
2025-04-01 3:03 ` Carlos Llamas [this message]
2025-04-01 7:53 ` Frode Isaksen
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-tXhrdTtV5t_P5p@google.com \
--to=cmllamas@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=fisaksen@baylibre.com \
--cc=frode@meta.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.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