From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Binder driver fixes for 6.19-final
Date: Sat, 7 Feb 2026 12:09:06 +0100 [thread overview]
Message-ID: <aYcdUltjnufW5zv7@kroah.com> (raw)
The following changes since commit 63804fed149a6750ffd28610c5c1c98cce6bd377:
Linux 6.19-rc7 (2026-01-25 14:11:24 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-6.19-final
for you to fetch changes up to ec4ddc90d201d09ef4e4bef8a2c6d9624525ad68:
binderfs: fix ida_alloc_max() upper bound (2026-02-03 12:59:07 +0100)
----------------------------------------------------------------
Binder fixes for 6.19-final
Here are some small, last-minute binder C and Rust driver fixes for
reported issues. They include a number of fixes for reported crashes
and other problems.
All of these have been in linux-next this week, and longer.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Alice Ryhl (2):
rust_binder: correctly handle FDA objects of length zero
rust_binder: add additional alignment checks
Carlos Llamas (4):
binder: fix UAF in binder_netlink_report()
binder: fix BR_FROZEN_REPLY error log
rust_binderfs: fix ida_alloc_max() upper bound
binderfs: fix ida_alloc_max() upper bound
drivers/android/binder.c | 19 +++++-
drivers/android/binder/rust_binderfs.c | 8 +--
drivers/android/binder/thread.rs | 109 +++++++++++++++++++++------------
drivers/android/binderfs.c | 8 +--
4 files changed, 94 insertions(+), 50 deletions(-)
next reply other threads:[~2026-02-07 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 11:09 Greg KH [this message]
2026-02-07 17:44 ` [GIT PULL] Binder driver fixes for 6.19-final pr-tracker-bot
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=aYcdUltjnufW5zv7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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