[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZWmI6QxlDuV-Miyr@google.com>
Date: Fri, 1 Dec 2023 07:19:05 +0000
From: Carlos Llamas <cmllamas@...gle.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Arve Hjønnevåg <arve@...roid.com>,
Christian Brauner <brauner@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Joel Fernandes <joel@...lfernandes.org>,
kernel-team@...roid.com, linux-kernel@...r.kernel.org,
Martijn Coenen <maco@...roid.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Todd Kjos <tkjos@...roid.com>
Subject: Re: [PATCH 16/21] binder: refactor page range allocation
On Tue, Nov 07, 2023 at 09:08:35AM +0000, Alice Ryhl wrote:
> Carlos Llamas <cmllamas@...gle.com> writes:
> > Instead of looping through the page range twice to first determine if
> > the mmap lock is required, simply do it per-page as needed. Split out
> > all this logic into a separate binder_get_user_page_remote() function.
> >
> > Signed-off-by: Carlos Llamas <cmllamas@...gle.com>
>
> One nit, otherwise looks okay to me.
> Reviewed-by: Alice Ryhl <aliceryhl@...gle.com>
>
> Carlos Llamas <cmllamas@...gle.com> writes:
> > + unsigned long index;
> > - size_t index;
>
> You're changing the type of index to unsigned long here, but it seems to
> me that size_t is the correct type.
Perhaps size_t made sense before the addresses were also moved to
unsigned long. I think this is a better fit now.
--
Carlos Llamas
Powered by blists - more mailing lists