From: Baoquan He <bhe@redhat.com>
To: Zhu Yanjun <yanjun.zhu@linux.dev>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] mm/gup: fix wrongly calculated returned value in fault_in_safe_writeable()
Date: Mon, 31 Mar 2025 06:48:25 +0800 [thread overview]
Message-ID: <Z+nKOYxiTWGNI9FQ@MiWiFi-R3L-srv> (raw)
In-Reply-To: <bb3d749f-c82f-4ba8-b1d2-10a38efb6199@linux.dev>
On 03/30/25 at 09:43pm, Zhu Yanjun wrote:
> 在 2025/3/30 14:17, Baoquan He 写道:
> > Not like fault_in_writeable() or fault_in_writeable(), in
> fault_in_readable()?
>
> In the above, one of the 2 fault_in_writeable should be fault_in_readable()
> ?
You are right, I will fix it in v2. Thanks.
> > fault_in_safe_writeable() local variable 'start' is increased page
> > by page to loop till the whole address range is handled. However,
> > it mistakenly calcalates the size of handled range with 'uaddr - start'.
> >
> > Fix it here.
> >
> > Signed-off-by: Baoquan He <bhe@redhat.com>
> > ---
> > mm/gup.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/mm/gup.c b/mm/gup.c
> > index 855ab860f88b..73777b1de679 100644
> > --- a/mm/gup.c
> > +++ b/mm/gup.c
> > @@ -2207,8 +2207,8 @@ size_t fault_in_safe_writeable(const char __user *uaddr, size_t size)
> > } while (start != end);
> > mmap_read_unlock(mm);
> > - if (size > (unsigned long)uaddr - start)
> > - return size - ((unsigned long)uaddr - start);
> > + if (size > start - (unsigned long)uaddr)
> > + return size - (start - (unsigned long)uaddr);
> > return 0;
> > }
> > EXPORT_SYMBOL(fault_in_safe_writeable);
>
>
next prev parent reply other threads:[~2025-03-30 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 12:17 [PATCH 0/7] mm/gup: Minor fix, cleanup and improvements Baoquan He
2025-03-30 12:17 ` [PATCH 1/7] mm/gup: fix wrongly calculated returned value in fault_in_safe_writeable() Baoquan He
2025-03-30 19:43 ` Zhu Yanjun
2025-03-30 22:48 ` Baoquan He [this message]
2025-03-30 12:17 ` [PATCH 2/7] mm/gup: check if both GUP_GET and GUP_PIN are set in __get_user_pages() earlier Baoquan He
2025-03-30 13:49 ` kernel test robot
2025-03-30 14:19 ` Baoquan He
2025-03-30 14:09 ` kernel test robot
2025-03-30 14:20 ` kernel test robot
2025-03-30 12:17 ` [PATCH 3/7] mm/gup: Fix the outdated code comments above get_user_pages_unlocked() Baoquan He
2025-03-31 13:58 ` Oscar Salvador
2025-03-31 15:19 ` Baoquan He
2025-03-30 12:17 ` [PATCH 4/7] mm/gup: remove gup_fast_pgd_leaf() and clean up the relevant codes Baoquan He
2025-03-30 12:17 ` [PATCH 5/7] x86/mm: remove pgd_leaf definition in arch Baoquan He
2025-03-30 12:17 ` [PATCH 6/7] x86/mm: remove p4d_leaf definition Baoquan He
2025-03-30 12:17 ` [PATCH 7/7] mm/pgtable: remove unneeded pgd_devmap() 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=Z+nKOYxiTWGNI9FQ@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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