Thread (23 messages) 23 messages, 9 authors, 2021-07-06

Re: [dpdk-dev] [RFC v2] porting AddressSanitizer feature to DPDK

From: Lin, Xueqin <hidden>
Date: 2021-06-30 08:16:03

-----Original Message-----
From: Burakov, Anatoly <redacted>
Sent: Monday, June 28, 2021 10:22 PM
To: David Marchand <redacted>; Lin, Xueqin
[off-list ref]
Cc: Jerin Jacob <redacted>; Peng, ZhihongX
[off-list ref]; Ananyev, Konstantin
[off-list ref]; Stephen Hemminger
[off-list ref]; dpdk-dev [off-list ref]
Subject: Re: [dpdk-dev] [RFC v2] porting AddressSanitizer feature to DPDK

On 18-Jun-21 10:04 AM, David Marchand wrote:
quoted
On Fri, Jun 18, 2021 at 9:49 AM Lin, Xueqin [off-list ref] wrote:
quoted
quoted
quoted
Suggest listing demo code and tool capture information for user to
try if
tool works, also add this part into doc.
quoted
quoted
# Also, Please update the release note for this feature.
Sure, we can update the release note if code merge.
Probably you can send v1 version next i.e change the RFC status to
get merged.
Sure, we will send v1 patch if no obvious objection for that, hope patch
could receive some ACKs and could success to merge, thanks.
quoted
How did you test this work?

UNH recently started testing with ASAN and it reveals leaks just in
the unit test.

Merging these annotations will help catch more issues.
But users will hit the current issues that we must fix first.
As far as i can tell, the regular build is not affected by this patch, so no issues
will be hit until someone actually runs the test. IMO it's better to merge it
early to catch more issues than to gate the feature on the condition that we
fix all bugs unrelated to this feature first.
Thanks for review and good feedback. 
--
Thanks,
Anatoly
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help