From: Joe Perches <joe@perches.com>
To: Ilan Tayari <ilant@mellanox.com>, Arnd Bergmann <arnd@arndb.de>,
Saeed Mahameed <saeedm@mellanox.com>
Cc: Matan Barak <matanb@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>,
Yossi Kuperman <yossiku@mellanox.com>,
Yevgeny Kliteynik <kliteyn@mellanox.com>,
Boris Pismenny <borisp@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/mlx5: IPSec, fix 64-bit division correctly
Date: Mon, 10 Jul 2017 08:45:43 -0700 [thread overview]
Message-ID: <1499701543.5468.11.camel@perches.com> (raw)
In-Reply-To: <AM4PR0501MB194094863514236D1BE04C62DBA90@AM4PR0501MB1940.eurprd05.prod.outlook.com>
On Mon, 2017-07-10 at 10:24 +0000, Ilan Tayari wrote:
> > -----Original Message-----
> > From: Arnd Bergmann [mailto:arnd@arndb.de]
> > Subject: [PATCH] net/mlx5: IPSec, fix 64-bit division correctly
> >
> > The new IPSec offload code introduced a build error:
> >
> > drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec_rxtx.o: In function
> > `mlx5e_ipsec_build_inverse_table':
> > ipsec_rxtx.c:(.text+0x556): undefined reference
> >
> > Another patch was added on top to fix the build error, but
> > that introduced a new bug, as we now use the remainder of
> > the division rather than the result.
Is it possible to return noise in mlx5e_ipsec_mss_inv ?
What clamps skb_shinfo(skb)->gso_size to MAX_LSO
(the size of inverse_table)?
#define MAX_LSO_MSS 2048
static __be16 mlx5e_ipsec_inverse_table[MAX_LSO_MSS];
static inline __be16 mlx5e_ipsec_mss_inv(struct sk_buff *skb)
{
return mlx5e_ipsec_inverse_table[skb_shinfo(skb)->gso_size];
}
next prev parent reply other threads:[~2017-07-10 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 9:37 [PATCH] net/mlx5: IPSec, fix 64-bit division correctly Arnd Bergmann
2017-07-10 9:57 ` Ilan Tayari
2017-07-10 10:24 ` Ilan Tayari
2017-07-10 15:45 ` Joe Perches [this message]
2017-07-10 18:34 ` David Miller
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=1499701543.5468.11.camel@perches.com \
--to=joe@perches.com \
--cc=arnd@arndb.de \
--cc=borisp@mellanox.com \
--cc=ilant@mellanox.com \
--cc=kliteyn@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=yossiku@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