From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Feng Li <lifeng1519@gmail.com>
Cc: Li Feng <fengli@smartx.com>,
David Marchand <david.marchand@redhat.com>,
Kyle Zhang <kyle@smartx.com>, dev <dev@dpdk.org>,
Yang Fan <fanyang@smartx.com>
Subject: Re: [dpdk-dev] [PATCH] eal: add madvise to avoid dump memory
Date: Thu, 23 Apr 2020 13:22:42 +0100 [thread overview]
Message-ID: <2c84372f-00c3-ed09-2cf5-fed1dff4b2bd@intel.com> (raw)
In-Reply-To: <CAEK8JBCdfZJiKNjDNgC9nDGLni9Dvw+U1doRFnh+zkAs5TXEsg@mail.gmail.com>
On 23-Apr-20 7:36 AM, Feng Li wrote:
> Hi,
> I have tested as follows, the core dump file is ~ 200KB.
> It should generate one core dump file each crash.
>
> #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 size = 1<<30;
> void* ptr = mmap(0, size , PROT_READ, MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
> if (ptr == (void*)-1) {
> perror("[-] mmap failed with MAP_PRIVATE | MAP_ANONYMOUS");
> exit(1);
> }
> if (madvise(ptr, size , MADV_DONTDUMP) != 0)
> perror("[-] madvise failed");
> while(1)
> sleep(1);
> return 0;
> }
>
That's odd, your code works. Mine, even though it did the same thing,
didn't work the same way. My compiler must like you more than it likes
me :) (or perhaps i had a typo...)
Anyway, i can see that this indeed prevents core dumps on madvise'd
memory (i've also tested it with PROT_NONE).
I'll go ahead and ack the original patch then.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-04-23 12:22 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
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 [this message]
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=2c84372f-00c3-ed09-2cf5-fed1dff4b2bd@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).