From: Michal Hocko <mhocko@suse.com>
To: Gaowei Pu <pugaowei@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org
Subject: Re: [PATCH v2] mm/mmap.c: use IS_ERR_VALUE to check return value of get_unmapped_area
Date: Tue, 15 Oct 2019 14:33:01 +0200 [thread overview]
Message-ID: <20191015123301.GC24932@dhcp22.suse.cz> (raw)
In-Reply-To: <20191012102512.28051-1-pugaowei@gmail.com>
On Sat 12-10-19 18:25:12, Gaowei Pu wrote:
> get_unmapped_area already cover the offset_in_page() check and returned
> with error ptr. So replace offset_in_page() with IS_ERR_VALUE().
I have to say that I found offset_in_page check quite unintuitive. It is
a relict from the past I suspect. A newer code seems to use
IS_ERR_VALUE. If we want to make the code consistent then I am for it.
Could you check other users as well? git grep suggests checking
kernel/events/uprobes.c, mm/mmap.c and mm/mremap.c.
I would simply use the following for the changelog
"
get_unmapped_area returns an address or -errno on failure. Historically
we have checked for the failure by offset_in_page() which is correct but
quite hard to read. Newer code started using IS_ERR_VALUE which is much
easier to read. Convert remaining users of offset_in_page as well.
This shouldn't introduce any functional changes.
"
> Signed-off-by: Gaowei Pu <pugaowei@gmail.com>
>
> V2: fix compile warnning.
> ---
> mm/mmap.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 7e8c3e8ae75f..6aebfeb6a486 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -1430,7 +1430,7 @@ unsigned long do_mmap(struct file *file, unsigned long addr,
> * that it represents a valid section of the address space.
> */
> addr = get_unmapped_area(file, addr, len, pgoff, flags);
> - if (offset_in_page(addr))
> + if (IS_ERR_VALUE(addr))
> return addr;
>
> if (flags & MAP_FIXED_NOREPLACE) {
> @@ -2990,15 +2990,16 @@ static int do_brk_flags(unsigned long addr, unsigned long len, unsigned long fla
> struct rb_node **rb_link, *rb_parent;
> pgoff_t pgoff = addr >> PAGE_SHIFT;
> int error;
> + unsigned long mapped_addr;
>
> /* Until we need other flags, refuse anything except VM_EXEC. */
> if ((flags & (~VM_EXEC)) != 0)
> return -EINVAL;
> flags |= VM_DATA_DEFAULT_FLAGS | VM_ACCOUNT | mm->def_flags;
>
> - error = get_unmapped_area(NULL, addr, len, 0, MAP_FIXED);
> - if (offset_in_page(error))
> - return error;
> + mapped_addr = get_unmapped_area(NULL, addr, len, 0, MAP_FIXED);
> + if (IS_ERR_VALUE(mapped_addr))
> + return mapped_addr;
>
> error = mlock_future_check(mm, mm->def_flags, len);
> if (error)
> --
> 2.23.0
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-10-15 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 10:25 Gaowei Pu
2019-10-15 12:33 ` Michal Hocko [this message]
2019-10-16 5:50 ` gaowei Pu
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=20191015123301.GC24932@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=pugaowei@gmail.com \
--cc=vbabka@suse.cz \
/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