From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B588DA0A0C; Thu, 1 Jul 2021 09:41:15 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7815640141; Thu, 1 Jul 2021 09:41:15 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id B60BB40040 for ; Thu, 1 Jul 2021 09:41:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1625125272; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=23lRaCaRL8wYCl5SfpiEHnRI7E0rrLpWo54JEQEx+9w=; b=XxZEkhHiOqi51pE7HuI84MZR2Tcnf1ps5cKkYr0UyUHJFFpq+QAFQDTAZTuME+eiNd6K8k 8WdRIcQQmLxaPfYnCqOZqCP8KTEJbULe4UlOJelgR8vJIwxQMNFYdX/dRHzjEb29Aw28R+ 78YpCiAK7n4Q/blJpUx55p7f0zMyeVU= Received: from mail-ua1-f69.google.com (mail-ua1-f69.google.com [209.85.222.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-555-Hx4lpzapMre2UxPIo_O5BQ-1; Thu, 01 Jul 2021 03:41:02 -0400 X-MC-Unique: Hx4lpzapMre2UxPIo_O5BQ-1 Received: by mail-ua1-f69.google.com with SMTP id y22-20020ab063960000b02902782db6cf24so1380830uao.20 for ; Thu, 01 Jul 2021 00:41:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=23lRaCaRL8wYCl5SfpiEHnRI7E0rrLpWo54JEQEx+9w=; b=j7qnizSRPsJkvfJuGuWqbbXhKlM2T+Q2FXLMk927FtnDHpFA5Q75bCsJOLSpLs5Hv1 mKiyCfJ7gUMt4HOR2xwyUV6vVNgZ4YC0k7hshm7WDDxy/nO2oEQwesBkMJ0/7u8F/nF4 jt7bdp1Ktq4u+vOuOa7LdWgRbMRK0E22rrpGPriBTQ0+OivalU5j8u0Fm1WDgYDYs9la MxPdiVUFI2FFMlZ7SW0ryWuAG607MlQWNwxpE16SSj5DtFue/aApr229JMIrsGNoIsDp 7qO84ytsSgtEhrcGI0kGurfEOrK9ikCo9TLuqsiR7IJDdde04rIozQ7RX0zh+oSxB5rF i6aw== X-Gm-Message-State: AOAM533Erxx556LM1kaz56zMaXslPvnrd2RNRkdcDVk8Qh40Z0wYIVxZ QqOcBfmnAtnpUUgNo/fvQ9inZI+3uqnLlRNs+rAJCM37sk+uD9O/t5TzZsxFM2ciGjujV5ANDuo xaZMN96WKhStolb0F0WE= X-Received: by 2002:a67:c513:: with SMTP id e19mr36345920vsk.18.1625125261639; Thu, 01 Jul 2021 00:41:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyLhBy21nzbAggHW9JnLPR+9OVMStaUT1K+F4LH+Yc9Qh8/IdkqSYsvH2b37fXSjshaIdhOqJfn0K438qtg3CA= X-Received: by 2002:a67:c513:: with SMTP id e19mr36345910vsk.18.1625125261404; Thu, 01 Jul 2021 00:41:01 -0700 (PDT) MIME-Version: 1.0 References: <20210610051352.48493-1-zhihongx.peng@intel.com> <20210615081205.101071-1-zhihongx.peng@intel.com> <8af553e7-29e1-b46d-dc68-32efaa17c9c0@intel.com> In-Reply-To: From: David Marchand Date: Thu, 1 Jul 2021 09:40:50 +0200 Message-ID: To: "Lin, Xueqin" , "Burakov, Anatoly" Cc: Jerin Jacob , "Peng, ZhihongX" , "Ananyev, Konstantin" , Stephen Hemminger , dpdk-dev Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [RFC v2] porting AddressSanitizer feature to DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Jul 1, 2021 at 8:48 AM Lin, Xueqin 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. Are all identified issues reported in dpdk.org bugzilla? It would help to have a hint in the bzs title, like "caught with ASAN". 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. Thanks. -- David Marchand