From: Alexey Dobriyan <adobriyan@gmail.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH 1/2] elf: simpler check for -EEXIST
Date: Fri, 15 Mar 2019 19:05:17 +0300 [thread overview]
Message-ID: <20190315160517.GA2135@avx2> (raw)
In-Reply-To: <52458645-823f-825e-660f-7b01d5dbb979@i-love.sakura.ne.jp>
On Fri, Mar 15, 2019 at 07:02:23AM +0900, Tetsuo Handa wrote:
> On 2019/03/15 5:42, Alexey Dobriyan wrote:
> > PTR_ERR((void *)map_addr) == -EEXIST
> >
> > is a very complicated way of doing the obvious.
>
> Michal suggested me to explicitly use PTR_ERR()
without any explanation why...
I wonder what documentation does this line need?
map_addr == -EEXIST
> for documentation purpose in
> a reply mail to https://lkml.kernel.org/r/20180418115546.GZ17484@dhcp22.suse.cz .
>
> >
> > Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> > ---
> >
> > fs/binfmt_elf.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > --- a/fs/binfmt_elf.c
> > +++ b/fs/binfmt_elf.c
> > @@ -375,8 +375,7 @@ static unsigned long elf_map(struct file *filep, unsigned long addr,
> > } else
> > map_addr = vm_mmap(filep, addr, size, prot, type, off);
> >
> > - if ((type & MAP_FIXED_NOREPLACE) &&
> > - PTR_ERR((void *)map_addr) == -EEXIST)
> > + if ((type & MAP_FIXED_NOREPLACE) && map_addr == -EEXIST)
> > pr_info("%d (%s): Uhuuh, elf segment at %px requested but the memory is mapped already\n",
> > task_pid_nr(current), current->comm, (void *)addr);
> >
> >
>
next prev parent reply other threads:[~2019-03-15 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 20:42 [PATCH 1/2] elf: simpler check for -EEXIST Alexey Dobriyan
2019-03-14 22:02 ` Tetsuo Handa
2019-03-15 16:05 ` Alexey Dobriyan [this message]
2019-03-16 8:31 ` Michal Hocko
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=20190315160517.GA2135@avx2 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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