From: Andreas Schwab <schwab@suse.de>
To: Andrew Senkevich <andrew.n.senkevich@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
libc-alpha <libc-alpha@sourceware.org>,
Max Horn <max@quendi.de>,
thomas@grindinggear.com
Subject: Re: [PATCH] Fix i386 memmove issue [BZ #22644]
Date: Mon, 19 Mar 2018 13:11:00 -0000 [thread overview]
Message-ID: <mvmlgeojjmi.fsf@suse.de> (raw)
In-Reply-To: <CAMXFM3vA=-LSK5VtKhhbs0g9faBdG0GjoAbNb6OPEbSt8dAA7A@mail.gmail.com> (Andrew Senkevich's message of "Mon, 19 Mar 2018 13:45:43 +0100")
On Mär 19 2018, Andrew Senkevich <andrew.n.senkevich@gmail.com> wrote:
> +static void
> +do_test2 (void)
> +{
> + uint32_t num = 0x20000000;
> + uint32_t * large_buf;
> +
> + large_buf = mmap ((void*)0x70000000, num, PROT_READ | PROT_WRITE,
> + MAP_PRIVATE | MAP_ANON | MAP_FIXED, -1, 0);
Since you are using MAP_FIXED this may overwrite an existing mapping.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-03-19 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 10:13 Andrew Senkevich
2018-02-19 10:31 ` Andreas Schwab
2018-03-14 14:43 ` Andrew Senkevich
2018-03-14 14:59 ` H.J. Lu
2018-03-19 12:46 ` Andrew Senkevich
2018-03-19 12:55 ` H.J. Lu
2018-03-19 13:11 ` Andreas Schwab [this message]
2018-03-19 13:17 ` Florian Weimer
2018-03-19 14:01 ` Andrew Senkevich
2018-03-19 14:25 ` Szabolcs Nagy
2018-03-19 15:33 ` Florian Weimer
2018-03-19 17:52 ` Andrew Senkevich
2018-03-19 17:57 ` H.J. Lu
2018-03-19 19:30 ` Andrew Senkevich
2018-03-19 19:38 ` H.J. Lu
2018-03-19 20:33 ` Andrew Senkevich
2018-03-19 20:50 ` H.J. Lu
2018-03-20 8:58 ` Andreas Schwab
2018-03-23 17:15 ` Andrew Senkevich
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=mvmlgeojjmi.fsf@suse.de \
--to=schwab@suse.de \
--cc=andrew.n.senkevich@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=max@quendi.de \
--cc=thomas@grindinggear.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).