From: Colin Ian King <colin.king@canonical.com>
To: Raed Salem <raeds@mellanox.com>
Cc: Boris Pismenny <borisp@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-rdma@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: re: net/mlx5: IPsec, Refactor SA handle creation and destruction
Date: Tue, 21 Apr 2020 14:59:56 +0100 [thread overview]
Message-ID: <ffb0bca8-003f-bb7a-51ac-171b1f4e4a75@canonical.com> (raw)
Hi,
Static analysis with Coverity has detected a potential issue with the
following commit:
commit 7dfee4b1d79e1800818abcfb47747b162c9a2d31
Author: Raed Salem <raeds@mellanox.com>
Date: Wed Oct 23 17:04:13 2019 +0300
net/mlx5: IPsec, Refactor SA handle creation and destruction
The issue is in mlx5_fpga_is_ipsec_device() in
drivers/net/ethernet/mellanox/mlx5/core/fpga/ipsec.c as follows:
710 Bitwise-and with zero
bit_and_with_zero: accel_xfrm->attrs.action &
MLX5_ACCEL_ESP_ACTION_DECRYPT is always 0. This occurs as the logical
operand of if.
711 if (accel_xfrm->attrs.action & MLX5_ACCEL_ESP_ACTION_DECRYPT) {
Logically dead code (DEADCODE)
712 err = ida_simple_get(&fipsec->halloc, 1, 0, GFP_KERNEL);
713 if (err < 0) {
714 context = ERR_PTR(err);
715 goto exists;
716 }
717
718 sa_ctx->sa_handle = err;
719 if (sa_handle)
720 *sa_handle = sa_ctx->sa_handle;
721 }
in include/linux/mlx5/accel.h MLX5_ACCEL_ESP_ACTION_DECRYPT is defined
as zero:
50 enum mlx5_accel_esp_action {
51 MLX5_ACCEL_ESP_ACTION_DECRYPT,
52 MLX5_ACCEL_ESP_ACTION_ENCRYPT,
53 };
I believe there are some other instances of this bit-wise and-ing with
zero, e.g. in mlx5_fpga_ipsec_release_sa_ctx() we have:
855 if (sa_ctx->fpga_xfrm->accel_xfrm.attrs.action &
856 MLX5_ACCEL_ESP_ACTION_DECRYPT)
Colin
next reply other threads:[~2020-04-21 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 13:59 Colin Ian King [this message]
2020-04-23 7:21 ` Raed Salem
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=ffb0bca8-003f-bb7a-51ac-171b1f4e4a75@canonical.com \
--to=colin.king@canonical.com \
--cc=borisp@mellanox.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raeds@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.com \
/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
all inboxes | Powered by JetHome®