From: David Hildenbrand <david@redhat.com>
To: Baoquan He <bhe@redhat.com>, linux-mm@kvack.org
Cc: akpm@linux-foundation.org, osalvador@suse.de,
yanjun.zhu@linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/4] mm/gup: clean up codes in fault_in_xxx() functions
Date: Fri, 11 Apr 2025 10:54:09 +0200 [thread overview]
Message-ID: <f03f7e13-3d37-4d4a-87a6-61731744f476@redhat.com> (raw)
In-Reply-To: <20250410035717.473207-5-bhe@redhat.com>
On 10.04.25 05:57, Baoquan He wrote:
> The code style in fault_in_readable() and fault_in_writable() is a
> little inconsistent with fault_in_safe_writeable(). In fault_in_readable()
> and fault_in_writable(), it uses 'uaddr' passed in as loop cursor. While
> in fault_in_safe_writeable(), local variable 'start' is used as loop
> cursor. This may mislead people when reading code or making change in
> these codes.
>
> Here define explicit loop cursor and use for loop to simplify codes in
> these three functions. These cleanup can make them be consistent in
> code style and improve readability.
>
> Signed-off-by: Baoquan He <bhe@redhat.com>
> ---
> mm/gup.c | 65 +++++++++++++++++++++++---------------------------------
> 1 file changed, 26 insertions(+), 39 deletions(-)
>
> diff --git a/mm/gup.c b/mm/gup.c
> index 77a5bc622567..a76bd7e90a71 100644
> --- a/mm/gup.c
> +++ b/mm/gup.c
> @@ -2113,28 +2113,24 @@ static long __get_user_pages_locked(struct mm_struct *mm, unsigned long start,
> */
> size_t fault_in_writeable(char __user *uaddr, size_t size)
> {
> - char __user *start = uaddr, *end;
> + const unsigned long start = (unsigned long)uaddr;
> + const unsigned long end = start + size;
> + unsigned long cur = start;
I would initialize cur in the for loop header, makes the loop easier to
read.
>
> if (unlikely(size == 0))
> return 0;
> +
Would not add that line to keep it like fault_in_readable() below.
> if (!user_write_access_begin(uaddr, size))
> return size;
> - if (!PAGE_ALIGNED(uaddr)) {
> - unsafe_put_user(0, uaddr, out);
> - uaddr = (char __user *)PAGE_ALIGN((unsigned long)uaddr);
> - }
> - end = (char __user *)PAGE_ALIGN((unsigned long)start + size);
> - if (unlikely(end < start))
> - end = NULL;
> - while (uaddr != end) {
> - unsafe_put_user(0, uaddr, out);
> - uaddr += PAGE_SIZE;
> - }
> +
> + /* Stop once we overflow to 0. */
> + for (; cur && cur < end; cur = PAGE_ALIGN_DOWN(cur + PAGE_SIZE))
> + unsafe_put_user(0, (char __user *)cur, out);
>
Staring at fault_in_safe_writeable(), we could also do
/* Stop once we overflow to 0. */
end = PAGE_ALIGN(end)
if (start < end)
end = 0;
for (cur = start; cur != end; cur = PAGE_ALIGN_DOWN(cur + PAGE_SIZE))
unsafe_put_user(0, (char __user *)cur, out);
Essentially, removing the "cur" check from the loop condition. Not sure
if that is better.
In any case, if all functions later look similar and clearer it's a big win.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-11 8:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 3:57 [PATCH v4 0/4] mm/gup: Minor fix, cleanup and improvements Baoquan He
2025-04-10 3:57 ` [PATCH v4 1/4] mm/gup: fix wrongly calculated returned value in fault_in_safe_writeable() Baoquan He
2025-04-10 8:31 ` Oscar Salvador
2025-04-11 3:43 ` Andrew Morton
2025-04-11 5:32 ` Baoquan He
2025-04-11 15:07 ` Andreas Gruenbacher
2025-04-11 23:22 ` Andrew Morton
2025-04-11 8:44 ` David Hildenbrand
2025-04-10 3:57 ` [PATCH v4 2/4] mm/gup: remove unneeded checking in follow_page_pte() Baoquan He
2025-04-10 3:57 ` [PATCH v4 3/4] mm/gup: remove gup_fast_pgd_leaf() and clean up the relevant codes Baoquan He
2025-04-10 3:57 ` [PATCH v4 4/4] mm/gup: clean up codes in fault_in_xxx() functions Baoquan He
2025-04-11 8:54 ` David Hildenbrand [this message]
2025-04-11 11:15 ` Baoquan He
2025-04-11 11:41 ` David Hildenbrand
2025-04-13 1:07 ` Baoquan He
2025-04-13 20:02 ` David Hildenbrand
2025-04-13 2:04 ` [PATCH v5 " Baoquan He
2025-04-13 20:09 ` David Hildenbrand
2025-04-14 3:44 ` Baoquan He
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=f03f7e13-3d37-4d4a-87a6-61731744f476@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=yanjun.zhu@linux.dev \
/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