From: Alice Ryhl <aliceryhl@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Carlos Llamas <cmllamas@google.com>,
Jann Horn <jannh@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-mm@kvack.org, "Alice Ryhl" <aliceryhl@google.com>,
stable@vger.kernel.org
Subject: [PATCH 0/2] Fix VMA confusion in Rust Binder
Date: Tue, 17 Feb 2026 14:22:37 +0000 [thread overview]
Message-ID: <20260217-binder-vma-check-v1-0-1a2b37f7b762@google.com> (raw)
This series contains two bugfixes for Rust Binder. I'd like to follow
them up with better solutions by changing the VMA api, but as an
immediate fix this should work.
See the first commit for an explanation of the actual bug.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Alice Ryhl (2):
rust_binder: check ownership before using vma
rust_binder: avoid reading the written value in offsets array
drivers/android/binder/page_range.rs | 78 +++++++++++++++++++++++++++---------
drivers/android/binder/thread.rs | 17 +++-----
2 files changed, 64 insertions(+), 31 deletions(-)
---
base-commit: 0f2acd3148e0ef42bdacbd477f90e8533f96b2ac
change-id: 20260217-binder-vma-check-b6fca42e986c
Best regards,
--
Alice Ryhl <aliceryhl@google.com>
next reply other threads:[~2026-02-17 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 14:22 Alice Ryhl [this message]
2026-02-17 14:22 ` [PATCH 1/2] rust_binder: check ownership before using vma Alice Ryhl
2026-02-17 15:13 ` Danilo Krummrich
2026-02-17 20:12 ` Alice Ryhl
2026-02-17 20:24 ` Miguel Ojeda
2026-02-17 20:36 ` Danilo Krummrich
2026-02-17 16:54 ` Jann Horn
2026-02-17 20:15 ` Alice Ryhl
2026-02-17 20:25 ` Jann Horn
2026-02-17 14:22 ` [PATCH 2/2] rust_binder: avoid reading the written value in offsets array Alice Ryhl
2026-02-17 16:35 ` Jann Horn
2026-02-17 20:03 ` Alice Ryhl
2026-02-17 21:17 ` kernel test robot
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=20260217-binder-vma-check-v1-0-1a2b37f7b762@google.com \
--to=aliceryhl@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tmgross@umich.edu \
/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