DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: jean.tourrilhes@hpe.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/1 v2] eal: Fix misleading error messages, errno can't be trusted.
Date: Mon, 3 Oct 2016 14:25:40 +0100	[thread overview]
Message-ID: <4a84de40-04b9-da6d-aeb9-ce661a9ebad5@intel.com> (raw)
In-Reply-To: <20160921211049.GA27472@labs.hpe.com>

Hi Jean,

There are some format issues with the patch:

You can run scripts/check-git-log.sh to check them:
Wrong headline format:
         eal: Fix misleading error messages, errno can't be trusted.
Wrong headline uppercase:
         eal: Fix misleading error messages, errno can't be trusted.
Missing 'Fixes' tag:
         eal: Fix misleading error messages, errno can't be trusted.

The script's output highlights the different issues.


On 21/09/2016 22:10, Jean Tourrilhes wrote:
>   lib/librte_eal/linuxapp/eal/eal.c        | 14 +++++++++++---
>   lib/librte_eal/linuxapp/eal/eal_memory.c | 16 ++++++++++++----
>   2 files changed, 23 insertions(+), 7 deletions(-)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal.c b/lib/librte_eal/linuxapp/eal/eal.c
> index 3fb2188..5df9f6a 100644
> --- a/lib/librte_eal/linuxapp/eal/eal.c
> +++ b/lib/librte_eal/linuxapp/eal/eal.c
> @@ -238,7 +238,8 @@ rte_eal_config_attach(void)
>   	mem_config = (struct rte_mem_config *) mmap(NULL, sizeof(*mem_config),
>   			PROT_READ, MAP_SHARED, mem_cfg_fd, 0);
>   	if (mem_config == MAP_FAILED)
> -		rte_panic("Cannot mmap memory for rte_config\n");
> +		rte_panic("Cannot mmap memory for rte_config! error %i (%s)\n",
> +			  errno, strerror(errno));
>   
>   	rte_config.mem_config = mem_config;
>   }
> @@ -263,9 +264,16 @@ rte_eal_config_reattach(void)
>   	mem_config = (struct rte_mem_config *) mmap(rte_mem_cfg_addr,
>   			sizeof(*mem_config), PROT_READ | PROT_WRITE, MAP_SHARED,
>   			mem_cfg_fd, 0);
> +	if (mem_config == MAP_FAILED || mem_config != rte_mem_cfg_addr) {
> +		if (mem_config != MAP_FAILED)
> +			/* errno is stale, don't use */
> +			rte_panic("Cannot mmap memory for rte_config at [%p], got [%p] - please use '--base-virtaddr' option\n",
> +				  rte_mem_cfg_addr, mem_config);
> +		else
> +			rte_panic("Cannot mmap memory for rte_config! error %i (%s)\n",
> +				  errno, strerror(errno));
> +	}
>   	close(mem_cfg_fd);
> -	if (mem_config == MAP_FAILED || mem_config != rte_mem_cfg_addr)
> -		rte_panic("Cannot mmap memory for rte_config\n");
>   

NIT but any reason you moved the check before closing the file 
descriptor? (not that it matters with current code as we panic anyway)

Thanks,
Sergio

>   	rte_config.mem_config = mem_config;
>   }
> diff --git a/lib/librte_eal/linuxapp/eal/eal_memory.c b/lib/librte_eal/linuxapp/eal/eal_memory.c
> index 41e0a92..b036ffc 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_memory.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_memory.c
> @@ -1615,10 +1615,18 @@ rte_eal_hugepage_attach(void)
>   				 PROT_READ, MAP_PRIVATE, fd_zero, 0);
>   		if (base_addr == MAP_FAILED ||
>   		    base_addr != mcfg->memseg[s].addr) {
> -			RTE_LOG(ERR, EAL, "Could not mmap %llu bytes "
> -				"in /dev/zero to requested address [%p]: '%s'\n",
> -				(unsigned long long)mcfg->memseg[s].len,
> -				mcfg->memseg[s].addr, strerror(errno));
> +			if (base_addr != MAP_FAILED)
> +				/* errno is stale, don't use */
> +				RTE_LOG(ERR, EAL, "Could not mmap %llu bytes "
> +					"in /dev/zero at [%p], got [%p] - "
> +					"please use '--base-virtaddr' option\n",
> +					(unsigned long long)mcfg->memseg[s].len,
> +					mcfg->memseg[s].addr, base_addr);
> +			else
> +				RTE_LOG(ERR, EAL, "Could not mmap %llu bytes "
> +					"in /dev/zero at [%p]: '%s'\n",
> +					(unsigned long long)mcfg->memseg[s].len,
> +					mcfg->memseg[s].addr, strerror(errno));
>   			if (aslr_enabled() > 0) {
>   				RTE_LOG(ERR, EAL, "It is recommended to "
>   					"disable ASLR in the kernel "

  reply	other threads:[~2016-10-03 13:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 21:10 Jean Tourrilhes
2016-10-03 13:25 ` Sergio Gonzalez Monroy [this message]
2016-10-03 15:55   ` Jean Tourrilhes
2016-10-03 16:15     ` Mcnamara, John
2016-10-03 16:34       ` Jean Tourrilhes
2016-10-03 20:46     ` Thomas Monjalon
2016-10-04  8:03       ` Sergio Gonzalez Monroy
2016-10-04  9:31         ` Thomas Monjalon
2016-10-04 17:17           ` [dpdk-dev] [PATCH v2 1/3] mem: fix hugepage mapping error messages Jean Tourrilhes
2016-10-04 19:07             ` Sergio Gonzalez Monroy
2016-10-05  9:51               ` Thomas Monjalon
2016-10-05 16:41                 ` Jean Tourrilhes
2016-10-03 16:07   ` [dpdk-dev] [PATCH 1/1 v2] eal: Fix misleading error messages, errno can't be trusted Jean Tourrilhes

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=4a84de40-04b9-da6d-aeb9-ce661a9ebad5@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=jean.tourrilhes@hpe.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).