All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Guan <Herbert.Guan@arm.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>,
	"jianbo.liu@linaro.org" <jianbo.liu@linaro.org>
Subject: Re: [PATCH v2] test: Fix memory corruption issues which fails the link_bonding test.
Date: Wed, 19 Jul 2017 01:54:03 +0000	[thread overview]
Message-ID: <HE1PR08MB2809C7122D2C7D6F7812434E86A60@HE1PR08MB2809.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <f1980db9-4cd1-4d2b-1e10-aa5f93e9e814@intel.com>

It's caused by some recent merges.  Applying this patch to 17.05 is okay.  I've identified the place of segfault, but there're still some other problems to this test case.

Thanks,
Herbert

-----Original Message-----
From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
Sent: Wednesday, July 19, 2017 0:14
To: Herbert Guan <Herbert.Guan@arm.com>; dev@dpdk.org; declan.doherty@intel.com; jianbo.liu@linaro.org
Subject: Re: [dpdk-dev] [PATCH v2] test: Fix memory corruption issues which fails the link_bonding test.

On 7/10/2017 12:13 PM, Herbert Guan wrote:
> Patch V2: fix build warnings by deleting unused variables.
>
> There were double-free problems in some test cases, which will cause a
> duplicated mbuf will be added into mempool.  After double-free, some
> new allocated mbuf will hold a same address and thus cause the memory
> corruption.
>
> Another minor issue is that in some test cases, allocated mbuf will
> not be released after test case exits.  Hopefully these leaked mbuf
> will be released by the next test case in its setup phase when
> stopping the virtual pmd ports, while this do is a memory leak of the
> exited test case.
>
> To fix above 2 issues, this patch will do:
> 1) Release virtual pmd ports' tx queue in the clean up function
>    remove_slaves_and_stop_bonded_device() of each test cases.
> 2) Do not release allocated mbufs for test bursts.  These mbufs
>    will be released in remove_slaves_and_stop_bonded_device() when
>    test case exits.
>
> Signed-off-by: Herbert Guan <herbert.guan@arm.com>

Updated unit test causing segfault, before and after patch, am I doing something wrong?

I will postpone this patch until unit test can be verified.

Thanks,
ferruh

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2017-07-19  1:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10  7:20 [PATCH] test: Fix memory corruption issues which fails the link_bonding test Herbert Guan
2017-07-10  7:55 ` Jianbo Liu
2017-07-10 11:13 ` [PATCH v2] " Herbert Guan
2017-07-12 10:23   ` Declan Doherty
2017-07-31 15:25     ` Ferruh Yigit
2017-07-18 16:13   ` Ferruh Yigit
2017-07-19  1:54     ` Herbert Guan [this message]
2017-07-12  9:59 ` [PATCH] " Declan Doherty
2017-07-12 10:16   ` Declan Doherty

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=HE1PR08MB2809C7122D2C7D6F7812434E86A60@HE1PR08MB2809.eurprd08.prod.outlook.com \
    --to=herbert.guan@arm.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jianbo.liu@linaro.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.