From: Steffen Klassert <steffen.klassert@secunet.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net] xfrm: fix a small bug in frm_sa_len()
Date: Fri, 10 Dec 2021 13:33:11 +0100 [thread overview]
Message-ID: <20211210123311.GK3272477@gauss3.secunet.de> (raw)
In-Reply-To: <20211208202019.3423010-1-eric.dumazet@gmail.com>
On Wed, Dec 08, 2021 at 12:20:19PM -0800, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> copy_user_offload() will actually push a struct struct xfrm_user_offload,
> which is different than (struct xfrm_state *)->xso
> (struct xfrm_state_offload)
>
> Fixes: d77e38e612a01 ("xfrm: Add an IPsec hardware offloading API")
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Steffen Klassert <steffen.klassert@secunet.com>
Applied to the ipsec tree, thanks Eric!
Note: I fixed a typo in the subject 'frm_sa_len -> xfrm_sa_len'
prev parent reply other threads:[~2021-12-10 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 20:20 [PATCH net] xfrm: fix a small bug in frm_sa_len() Eric Dumazet
2021-12-10 12:33 ` Steffen Klassert [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=20211210123311.GK3272477@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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