From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ivan Malov <ivan.malov@arknetworks.am>,
dev@dpdk.org
Cc: Artemii Morozov <artemii.morozov@arknetworks.am>, stable@dpdk.org
Subject: Re: [PATCH 1/1] net/sfc: drop redundant null check from IPv4 flow item parse
Date: Mon, 17 Jul 2023 14:17:31 +0100 [thread overview]
Message-ID: <777a5306-554f-e73e-66d6-55e66ab20754@amd.com> (raw)
In-Reply-To: <9c075a69-cb2e-3ca7-78ee-51aee51c0a6f@oktetlabs.ru>
On 7/14/2023 6:38 AM, Andrew Rybchenko wrote:
> On 7/14/23 01:40, Ivan Malov wrote:
>> Such check is already done at an earlier point, in
>> sfc_flow_parse_pattern(), so remove it from IPv4
>> item parser. Doing so should fix Coverity issue.
>>
>> Coverity issue: 395526
>> Fixes: f79ce621e963 ("net/sfc: support IPv4 fragment matching in
>> transfer rules")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Ivan Malov <ivan.malov@arknetworks.am>
>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-07-17 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 22:40 Ivan Malov
2023-07-14 5:38 ` Andrew Rybchenko
2023-07-17 13:17 ` Ferruh Yigit [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=777a5306-554f-e73e-66d6-55e66ab20754@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=artemii.morozov@arknetworks.am \
--cc=dev@dpdk.org \
--cc=ivan.malov@arknetworks.am \
--cc=stable@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).