> -----Original Message----- > From: David Marchand <david.march...@redhat.com> > Sent: Wednesday, November 3, 2021 1:29 AM > To: Lin, Xueqin <xueqin....@intel.com> > Cc: Peng, ZhihongX <zhihongx.p...@intel.com>; Thomas Monjalon > <tho...@monjalon.net>; Burakov, Anatoly <anatoly.bura...@intel.com>; > Ananyev, Konstantin <konstantin.anan...@intel.com>; Stephen Hemminger > <step...@networkplumber.org>; Dumitrescu, Cristian > <cristian.dumitre...@intel.com>; Mcnamara, John > <john.mcnam...@intel.com>; Richardson, Bruce > <bruce.richard...@intel.com>; dev <dev@dpdk.org>; Chen, Zhaoyan > <zhaoyan.c...@intel.com>; Tu, Lijuan <lijuan...@intel.com> > Subject: Re: [dpdk-dev] [PATCH v13 1/4] enable ASan AddressSanitizer > > On Mon, Nov 1, 2021 at 4:37 AM Lin, Xueqin <xueqin....@intel.com> wrote: > > > ASan is a really interesting tool, but there are still issues in some > components. > > > I caught a few and opened bugs. > > > > Are they DPDK bugs or this tool code bugs? > > DPDK bugs that I started reporting some weeks ago. > I mentionned it during CI call. > bzs can be queried via: https://bugs.dpdk.org/buglist.cgi?quicksearch=[asan] > Some fixes have been sent.
Cool, IC, we tracked some internal bugs in internal bug system, and public to report some common modules in bugzalla, such as 738 737 792 722 723 735... Most of patches have been sent and upstreamed, bugzalla remained below bug is not resolved. https://bugs.dpdk.org/show_bug.cgi?id=792 > > > Have you reported and tracked in bugzalla? Not sure if we captured them, as > you know, we used this tool to detect and found lots of DPDK bugs in various > of > components that static scan tool can't find. > > Not sure I understand. > Did you catch more issues but you did not report upstream? > > If so, please make them public. Sure, we will public them if they are common modules, also add flag [asan] in title to filter them. > > > -- > David Marchand
