From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Carlos Llamas <cmllamas@google.com>
Cc: stable@vger.kernel.org, "Arve Hjønnevåg" <arve@android.com>,
"Alice Ryhl" <aliceryhl@google.com>
Subject: Re: [PATCH 5.10.y] binder: fix max_thread type inconsistency
Date: Wed, 12 Jun 2024 14:27:32 +0200 [thread overview]
Message-ID: <2024061223-flap-playpen-bd16@gregkh> (raw)
In-Reply-To: <20240523184352.1541595-1-cmllamas@google.com>
On Thu, May 23, 2024 at 06:43:52PM +0000, Carlos Llamas wrote:
> commit 42316941335644a98335f209daafa4c122f28983 upstream.
>
> The type defined for the BINDER_SET_MAX_THREADS ioctl was changed from
> size_t to __u32 in order to avoid incompatibility issues between 32 and
> 64-bit kernels. However, the internal types used to copy from user and
> store the value were never updated. Use u32 to fix the inconsistency.
>
> Fixes: a9350fc859ae ("staging: android: binder: fix BINDER_SET_MAX_THREADS declaration")
> Reported-by: Arve Hjønnevåg <arve@android.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
> Link: https://lore.kernel.org/r/20240421173750.3117808-1-cmllamas@google.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> [cmllamas: resolve minor conflicts due to missing commit 421518a2740f]
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> ---
> drivers/android/binder.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-06-12 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 12:20 FAILED: patch "[PATCH] binder: fix max_thread type inconsistency" failed to apply to 5.10-stable tree gregkh
2024-05-23 18:43 ` [PATCH 5.10.y] binder: fix max_thread type inconsistency Carlos Llamas
2024-06-12 12:27 ` Greg Kroah-Hartman [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=2024061223-flap-playpen-bd16@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=cmllamas@google.com \
--cc=stable@vger.kernel.org \
/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