From: "Lin, Xueqin" <xueqin.lin@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Jerin Jacob <jerinjacobk@gmail.com>,
"Peng, ZhihongX" <zhihongx.peng@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC v2] porting AddressSanitizer feature to DPDK
Date: Fri, 2 Jul 2021 11:05:14 +0000 [thread overview]
Message-ID: <BN7PR11MB26585A5771B8EDE791935371941F9@BN7PR11MB2658.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8yN++8vojNRH5bbrTNYkddeMeQrQpNuv=1pmBxUJx-HWA@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, July 1, 2021 3:41 PM
> To: Lin, Xueqin <xueqin.lin@intel.com>; Burakov, Anatoly
> <anatoly.burakov@intel.com>
> Cc: Jerin Jacob <jerinjacobk@gmail.com>; Peng, ZhihongX
> <zhihongx.peng@intel.com>; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; Stephen Hemminger
> <stephen@networkplumber.org>; dpdk-dev <dev@dpdk.org>
> Subject: Re: [dpdk-dev] [RFC v2] porting AddressSanitizer feature to DPDK
>
> On Thu, Jul 1, 2021 at 8:48 AM Lin, Xueqin <xueqin.lin@intel.com> wrote:
> > We also captured this type issues and selected one, reported in internal
> system JARA and bugzilla in May.
> > Pls check https://bugs.dpdk.org/show_bug.cgi?id=722 for detail, some
> developers are analysis this issue in JIRA but not resolved so far, Anatoly
> should also know this.
>
> Thanks for sharing this.
>
>
> > It is DPDK issue, not this patch issue, it doesn't mean we not do much test.
> > We put all of thousands of regression cases as case list for this patch test,
> some issues still are tracking.
>
> Sorry, can you rephrase?
> I sure hope there are not thousands of issues with ASAN.
Relax, don't have so many issues.
I mean we have thousands of automation dpdk cases, run the cases for DPDK version build with Asan tool, check dpdk code if have memory issue.
Some issues are still WIP to check.
>
>
> Are all identified issues reported in dpdk.org bugzilla?
> It would help to have a hint in the bzs title, like "caught with ASAN".
No, we reported common issue to Bugzilla.
Good idea to add title.
>
> I can't find a report about the infinite loop on invalid fds, making a dpdk app
> unable to exit gracefully with ASAN enabled.
> But at least, I sent a fix for this, waiting for Anatoly to review.
> https://patchwork.dpdk.org/project/dpdk/patch/20210614091213.3953-1-
> david.marchand@redhat.com/
>
>
> > >
> > > Anyway, the memory allocator is your stuff, so your call.
> > >
> > > Prefix for the title of such a patch should be mem:
>
> Anatoly and Jerin like your patch, but it is still a RFC and there were
> comments on a missing release note update and unit test.
> Please address those comments and submit a regular patch.
Sure, we are preparing the v1 patch according to comment.
>
>
> Thanks.
>
> --
> David Marchand
next prev parent reply other threads:[~2021-07-02 11:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 5:13 [dpdk-dev] [RFC] " zhihongx.peng
2021-06-10 8:32 ` Bruce Richardson
2021-06-11 4:42 ` Lin, Xueqin
2021-06-10 9:12 ` Ananyev, Konstantin
2021-06-11 4:49 ` Lin, Xueqin
2021-06-10 20:03 ` Stephen Hemminger
2021-06-11 6:15 ` Lin, Xueqin
2021-06-15 8:12 ` [dpdk-dev] [RFC v2] " zhihongx.peng
2021-06-15 8:40 ` Jerin Jacob
2021-06-16 9:13 ` Lin, Xueqin
2021-06-16 11:34 ` Jerin Jacob
2021-06-18 7:48 ` Lin, Xueqin
2021-06-18 9:04 ` David Marchand
2021-06-22 3:26 ` Lin, Xueqin
2021-06-28 14:22 ` Burakov, Anatoly
2021-06-28 14:23 ` Jerin Jacob
2021-06-30 8:15 ` Lin, Xueqin
2021-06-30 8:34 ` David Marchand
2021-07-01 6:48 ` Lin, Xueqin
2021-07-01 7:40 ` David Marchand
2021-07-02 11:05 ` Lin, Xueqin [this message]
2021-07-06 20:40 ` David Christensen
2021-07-06 23:12 ` Stephen Hemminger
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=BN7PR11MB26585A5771B8EDE791935371941F9@BN7PR11MB2658.namprd11.prod.outlook.com \
--to=xueqin.lin@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinjacobk@gmail.com \
--cc=konstantin.ananyev@intel.com \
--cc=stephen@networkplumber.org \
--cc=zhihongx.peng@intel.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).