From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Lior Assouline <alior101@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: seg fault bug in rte_flow_classify.c in dpdk-21.11 and onward
Date: Thu, 7 Apr 2022 16:37:42 +0000 [thread overview]
Message-ID: <DM6PR11MB28906BA69185DAF6826814C6EFE69@DM6PR11MB2890.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CALN-Pg=84Of8pT7TBzTseVm1maRifpLTykwaLrTM1d5xOW04zQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 516 bytes --]
Hi Lior,
From: Lior Assouline <alior101@gmail.com>
Sent: Monday, March 28, 2022 4:10 PM
To: dev@dpdk.org
Subject: seg fault bug in rte_flow_classify.c in dpdk-21.11 and onward
when a buff of rx packets is given to that function, and some are a "hit" and some are not, there is a seg fault on the 0 pointers...
Unless I'm, missing something there should be a check on non zero
[cid:image001.png@01D84AA6.1FBF7FE0]
Would you like to send a patch, and I will review it.
Regards,
Bernard.
[-- Attachment #1.2: Type: text/html, Size: 3411 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 121359 bytes --]
prev parent reply other threads:[~2022-04-07 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 15:10 Lior Assouline
2022-04-07 16:37 ` Iremonger, Bernard [this message]
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=DM6PR11MB28906BA69185DAF6826814C6EFE69@DM6PR11MB2890.namprd11.prod.outlook.com \
--to=bernard.iremonger@intel.com \
--cc=alior101@gmail.com \
--cc=dev@dpdk.org \
/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).