netdev - Re: [PATCH 1/2] xfrm: add SA information to the offloaded packet

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADsK2K9mgZ=GSQQaNq_nBWCvGP41GQfwu2F0xUw48KWcCEaPEQ@mail.gmail.com>
Date: Wed, 6 Nov 2024 16:14:36 -0800
From: Feng Wang <wangfe@...gle.com>
To: antony.antony@...unet.com
Cc: Leon Romanovsky <leon@...nel.org>, netdev@...r.kernel.org, steffen.klassert@...unet.com
Subject: Re: [PATCH 1/2] xfrm: add SA information to the offloaded packet

Antony brought out an important function xfrm_lookup_with_ifid(), this
function returns the next dst_entry.

The xfrm_lookup_with_ifid() function utilizes xfrm_sk_policy_lookup()
to find a matching policy based on the given if_id. The if_id checking
is handled in it.
Once the policy is found, xfrm_resolve_and_create_bundle() determines
the correct Security Association (SA) and associates it with the
destination entry (dst->xfrm).
This SA information is then passed directly to the driver. Since the
kernel has already performed the necessary if_id checks for policy,
there's no need for the driver to duplicate this effort.