DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Li Feng <fengli@smartx.com>
Cc: dev@dpdk.org, stable@dpdk.org, kyle@smartx.com,
	lifeng1519@gmail.com, fanyang@smartx.com,
	david.marchand@redhat.com, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v6] eal: use madvise to exclude unmapped memory from being dumped
Date: Fri, 24 Apr 2020 16:20:50 +0100	[thread overview]
Message-ID: <47a6417f-97de-4dde-50b4-5bdeb00565d5@intel.com> (raw)
In-Reply-To: <20200424131905.18315-1-fengli@smartx.com>

On 24-Apr-20 2:19 PM, Li Feng wrote:
> Currently, even though memory is mapped with PROT_NONE, this does not
> cause it to be excluded from core dumps. This is counter-productive,
> because in a lot of cases, this memory will go unused (e.g. when the
> memory subsystem preallocates VA space but hasn't yet mapped physical
> pages into it).
> 
> Use `madvise()` call with MADV_DONTDUMP parameter to exclude the
> unmapped memory from being dumped.
> 
> Signed-off-by: Li Feng <fengli@smartx.com>
> ---
> v6:
> - use RTE_DONTDUMP in right place.
> 
> v5:
> - fix a code style.
> 
> V4:
> - simplify the code;
> - remove the undo code in V3;
> 
> V3:
> - add support for freebsd.
> - when free_seg is called, mark the memory MADV_DONTDUMP.
> - when alloc_seg is called, mark the memory MADV_DODUMP.
> 
>   lib/librte_eal/common/eal_common_memory.c | 17 +++++++++++++++++
>   lib/librte_eal/linux/eal_memalloc.c       |  3 +++
>   2 files changed, 20 insertions(+)
> 
> diff --git a/lib/librte_eal/common/eal_common_memory.c b/lib/librte_eal/common/eal_common_memory.c
> index cc7d54e0c..cd20672ce 100644
> --- a/lib/librte_eal/common/eal_common_memory.c
> +++ b/lib/librte_eal/common/eal_common_memory.c
> @@ -40,6 +40,14 @@
>   static void *next_baseaddr;
>   static uint64_t system_page_sz;
>   
> +#ifdef RTE_EXEC_ENV_LINUX
> +#define RTE_DONTDUMP MADV_DONTDUMP
> +#elif RTE_EXEC_ENV_FREEBSD
> +#define RTE_DONTDUMP MADV_NOCORE
> +#else
> +#error "madvise doesn't support this OS"
> +#endif
> +
>   #define MAX_MMAP_WITH_DEFINED_ADDR_TRIES 5
>   void *
>   eal_get_virtual_area(void *requested_addr, size_t *size,
> @@ -179,6 +187,15 @@ eal_get_virtual_area(void *requested_addr, size_t *size,
>   			munmap(aligned_end, after_len);
>   	}
>   
> +	if (!unmap) {
> +		/*
> +		 * Exclude this pages from a core dump.
> +		 */
> +		if (madvise(aligned_addr, *size, RTE_DONTDUMP) != 0)
> +			RTE_LOG(DEBUG, EAL, "madvise failed: %s\n",
> +				strerror(errno));
> +	}
> +
>   	return aligned_addr;
>   }
>   
> diff --git a/lib/librte_eal/linux/eal_memalloc.c b/lib/librte_eal/linux/eal_memalloc.c
> index af6d0d023..f628e0991 100644
> --- a/lib/librte_eal/linux/eal_memalloc.c
> +++ b/lib/librte_eal/linux/eal_memalloc.c
> @@ -687,6 +687,9 @@ free_seg(struct rte_memseg *ms, struct hugepage_info *hi,
>   		return -1;
>   	}
>   
> +	if (madvise(ms->addr, ms->len, MADV_DONTDUMP) != 0)
> +		RTE_LOG(DEBUG, EAL, "madvise failed: %s\n", strerror(errno));
> +
>   	exit_early = false;
>   
>   	/* if we're using anonymous hugepages, nothing to be done */
> 

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

-- 
Thanks,
Anatoly

  reply	other threads:[~2020-04-24 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 10:50 [dpdk-dev] [PATCH v2] " Li Feng
2020-04-24 11:23 ` Burakov, Anatoly
2020-04-24 11:36   ` Bruce Richardson
2020-04-24 11:46     ` Burakov, Anatoly
2020-04-24 12:37   ` Li Feng
2020-04-24 12:39 ` [dpdk-dev] [PATCH v4] " Li Feng
2020-04-24 12:53 ` [dpdk-dev] [PATCH v5] " Li Feng
2020-04-24 13:02   ` Bruce Richardson
2020-04-24 13:19 ` [dpdk-dev] [PATCH v6] " Li Feng
2020-04-24 15:20   ` Burakov, Anatoly [this message]
2020-04-24 17:33   ` David Marchand

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=47a6417f-97de-4dde-50b4-5bdeb00565d5@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@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 \
    --cc=stable@dpdk.org \
    /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).