From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Feng Li <lifeng1519@gmail.com>,
David Marchand <david.marchand@redhat.com>
Cc: Li Feng <fengli@smartx.com>, Kyle Zhang <kyle@smartx.com>,
dev <dev@dpdk.org>,
fanyang@smartx.com
Subject: Re: [dpdk-dev] [PATCH] eal: add madvise to avoid dump memory
Date: Tue, 21 Apr 2020 13:19:06 +0100 [thread overview]
Message-ID: <d1333190-a0ac-1f8c-4002-2326fa874110@intel.com> (raw)
In-Reply-To: <CAEK8JBCZrPZ6_FgZUNNtotPcsFFOn1_zEMHupUnJm7A72Z2u1w@mail.gmail.com>
On 21-Apr-20 12:06 PM, Feng Li wrote:
> #include <sys/mman.h>
> #include <time.h>
> #include <stdint.h>
> #include <unistd.h>
> #include <stdlib.h>
> #include <stdio.h>
>
> int main(int argc, char** argv) {
> // FIXME(fengli): XXXXX
> uint64_t gb = atoi(argv[1]);
> void* ptr = mmap(0, gb << 30, PROT_NONE, MAP_PRIVATE |
> MAP_ANONYMOUS, -1, 0);
> if (ptr == (void*)-1) {
> perror("[-] mmap failed with MAP_PRIVATE | MAP_ANONYMOUS");
> exit(1);
> }
> while(1)
> sleep(1);
> return 0;
> }
DONTDUMP is available since Linux 3.4. I presume our minimum kernel
version is higher than that.
I have little idea of how dumping works, but reading the manpage for
madvise, DONTDUMP should be the way to go here. Also, reading up on
PROT_NONE, i can't find any references to this memory necessarily being
excluded from core dumps.
That said, I've run the program above, and i got a core dump sized
~100K. Do i need any special configuration to trigger core dump that
would include that anonymous memory?
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-04-21 12:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200420070508.645533-1-fengli@smartx.com>
2020-04-20 7:07 ` Li Feng
2020-04-20 7:13 ` David Marchand
2020-04-20 9:40 ` Feng Li
2020-04-21 7:41 ` David Marchand
2020-04-21 11:06 ` Feng Li
2020-04-21 12:19 ` Burakov, Anatoly [this message]
2020-04-21 16:38 ` Feng Li
2020-04-21 17:02 ` Burakov, Anatoly
2020-04-22 3:13 ` Li Feng
2020-04-22 9:53 ` Burakov, Anatoly
[not found] ` <CAEK8JBCdfZJiKNjDNgC9nDGLni9Dvw+U1doRFnh+zkAs5TXEsg@mail.gmail.com>
2020-04-23 12:22 ` Burakov, Anatoly
2020-04-23 15:43 ` [dpdk-dev] [PATCH v2] " Li Feng
2020-04-23 16:33 ` Burakov, Anatoly
2020-04-23 20:04 ` David Marchand
2020-04-24 9:12 ` Burakov, Anatoly
2020-04-24 9:14 ` Bruce Richardson
2020-04-24 9:33 ` Feng Li
2020-04-24 11:00 ` Burakov, Anatoly
2020-04-24 12:03 ` Li Feng
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=d1333190-a0ac-1f8c-4002-2326fa874110@intel.com \
--to=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanyang@smartx.com \
--cc=fengli@smartx.com \
--cc=kyle@smartx.com \
--cc=lifeng1519@gmail.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 NNTP newsgroup(s).