From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id CBFA8A046B; Sat, 9 May 2020 08:21:52 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A2D7B1D939; Sat, 9 May 2020 08:21:52 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 9018D1D937 for ; Sat, 9 May 2020 08:21:50 +0200 (CEST) IronPort-SDR: 49hBP2n9HItgJ+gDWKNEzJ3sGgRchKZ1VIEoUGaSJBqo1O6idVAg3O5nb+O6+Rh87uwUf/F++E 5WbZC0BQm4fw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 May 2020 23:21:49 -0700 IronPort-SDR: +no1I3f9g6b6ITMF63XTwqK9TI9yW5fpJgWXDDpVLoJq94++vATeuVv9v/lXvatvGYVqhBLGxu NdNTWZLkScog== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,370,1583222400"; d="scan'208";a="296361947" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga002.fm.intel.com with ESMTP; 08 May 2020 23:21:49 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 8 May 2020 23:21:49 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.26]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.91]) with mapi id 14.03.0439.000; Sat, 9 May 2020 14:21:44 +0800 From: "Zhang, Qi Z" To: "Guo, Jia" , "Xing, Beilei" , "Ye, Xiaolong" , "Yang, Qiming" , "Wu, Jingjing" CC: "dev@dpdk.org" , "Lu, Wenzhuo" Thread-Topic: [PATCH] net/iavf: fix rte flow error log issue Thread-Index: AQHWJRbtUp6hbrhcvUG2uU6g3wCKyKifSegQ Date: Sat, 9 May 2020 06:21:44 +0000 Message-ID: <039ED4275CED7440929022BC67E7061154812A44@SHSMSX103.ccr.corp.intel.com> References: <20200508205830.52437-1-jia.guo@intel.com> In-Reply-To: <20200508205830.52437-1-jia.guo@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] net/iavf: fix rte flow error log issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" > -----Original Message----- > From: Guo, Jia > Sent: Saturday, May 9, 2020 4:59 AM > To: Xing, Beilei ; Ye, Xiaolong > ; Yang, Qiming ; Wu, > Jingjing > Cc: Zhang, Qi Z ; dev@dpdk.org; Lu, Wenzhuo > ; Guo, Jia > Subject: [PATCH] net/iavf: fix rte flow error log issue >=20 > When processing a rte flow, such as creating a parse engine, or creating = or > destroying a rss rule, if they are failed, they all need to construct the= flow > error structure before return the error message back to app. If not so, i= t will > cause app crash when app printing the message out of a flow error. >=20 > Fixes: 7be10c3004be ("net/iavf: add RSS configuration for VF") > Fixes: ff2d0c345c3b ("net/iavf: support generic flow API") > Signed-off-by: Jeff Guo Acked-by: Qi Zhang