From: Olivier MATZ <olivier.matz@6wind.com>
To: Dan Aloni <dan@kernelim.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] mempool: fix the inverted pg_num check on create
Date: Mon, 17 Aug 2015 10:55:35 +0200 [thread overview]
Message-ID: <55D1A187.7080802@6wind.com> (raw)
In-Reply-To: <1439752099-23090-1-git-send-email-dan@kernelim.com>
Hi,
On 08/16/2015 09:08 PM, Dan Aloni wrote:
> The rest of the code expects pg_num <= RTE_DIM(mp->elt_pa).
>
> Signed-off-by: Dan Aloni <dan@kernelim.com>
> ---
> lib/librte_mempool/rte_mempool.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_mempool/rte_mempool.c b/lib/librte_mempool/rte_mempool.c
> index 8e185c545479..edcfa8bf9cb1 100644
> --- a/lib/librte_mempool/rte_mempool.c
> +++ b/lib/librte_mempool/rte_mempool.c
> @@ -461,7 +461,7 @@ rte_mempool_xmem_create(const char *name, unsigned n, unsigned elt_size,
> }
>
> /* Check that pg_num and pg_shift parameters are valid. */
> - if (pg_num < RTE_DIM(mp->elt_pa) || pg_shift > MEMPOOL_PG_SHIFT_MAX) {
> + if (pg_num > RTE_DIM(mp->elt_pa) || pg_shift > MEMPOOL_PG_SHIFT_MAX) {
> rte_errno = EINVAL;
> return NULL;
> }
>
Could you give some details about the conditions to reproduce and the
consequences of the issue?
>From what I see, RTE_DIM(mp->elt_pa) is always 1:
#define MEMPOOL_PG_NUM_DEFAULT 1
struct rte_mempool {
...
phys_addr_t elt_pa[MEMPOOL_PG_NUM_DEFAULT];
} __rte_cache_aligned;
>From rte_mempool_xmem_create() documentation, pg_num gives the size of
the paddr array, which is allocated by the caller. So I think there is
no issue here.
Regards,
Olivier
next prev parent reply other threads:[~2015-08-17 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 19:08 [PATCH] mempool: fix the inverted pg_num check on create Dan Aloni
2015-08-17 8:55 ` Olivier MATZ [this message]
2015-08-17 10:50 ` Dan Aloni
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=55D1A187.7080802@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dan@kernelim.com \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.