From: Artem Lytkin <iprintercanon@gmail.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Danilo Krummrich <dakr@kernel.org>, Jann Horn <jannh@google.com>,
Carlos Llamas <cmllamas@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Almeida <daniel.almeida@collabora.com>,
Deborah Brouwer <deborah.brouwer@collabora.com>,
linux-mm@kvack.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] rust_binder: check ownership before using vma
Date: Tue, 25 Aug 2026 12:24:25 +0300 [thread overview]
Message-ID: <20260825092425.64784-1-iprintercanon@gmail.com> (raw)
In-Reply-To: <ao1E_6yo9hE17e2E@google.com>
On Tue, Aug 25, 2026 at 07:32:15AM +0000, Alice Ryhl wrote:
> I'd be happy to let someone else work on it, but it's somewhat
> nontrivial, so perhaps we should have a call to discuss the design to
> work out the details?
A call is hard for me to fit in at the moment, sorry. Could we do it
over mail instead, here or off-list, whichever suits you? I'll write
the design up in the next few days and you reply whenever you get to
it. If your vm_open draft is still around I'd gladly start form it.
Artem
next prev parent reply other threads:[~2026-08-25 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 11:53 [PATCH v2 0/2] Fix VMA confusion in Rust Binder Alice Ryhl
2026-02-18 11:53 ` [PATCH v2 1/2] rust_binder: check ownership before using vma Alice Ryhl
2026-02-18 13:47 ` Danilo Krummrich
2026-02-18 15:54 ` Liam R. Howlett
2026-02-18 16:39 ` Alice Ryhl
2026-03-02 17:18 ` Carlos Llamas
2026-03-02 17:28 ` Jann Horn
2026-03-02 18:36 ` Carlos Llamas
2026-08-24 19:48 ` Artem Lytkin
2026-08-24 20:55 ` Lorenzo Stoakes (ARM)
2026-08-25 7:32 ` Alice Ryhl
2026-08-25 9:24 ` Artem Lytkin [this message]
2026-08-25 10:44 ` Lorenzo Stoakes (ARM)
2026-02-18 11:53 ` [PATCH v2 2/2] rust_binder: avoid reading the written value in offsets array Alice Ryhl
2026-02-18 16:02 ` Liam R. Howlett
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=20260825092425.64784-1-iprintercanon@gmail.com \
--to=iprintercanon@gmail.com \
--cc=aliceryhl@google.com \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=deborah.brouwer@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=rust-for-linux@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
all inboxes | Powered by JetHome®