netdev - Re: [PATCH 8/11] [IPSEC]: Store afinfo pointer in xfrm

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: <20071017.213419.52167434.davem@davemloft.net>
Date:	Wed, 17 Oct 2007 21:34:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	yoshfuji@...ux-ipv6.org, kaber@...sh.net, netdev@...r.kernel.org
Subject: Re: [PATCH 8/11] [IPSEC]: Store afinfo pointer in xfrm_mode

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Wed, 17 Oct 2007 22:34:16 +0800

> [IPSEC]: Store afinfo pointer in xfrm_mode
> 
> It is convenient to have a pointer from xfrm_state to address-specific
> functions such as the output function for a family.  Currently the
> address-specific policy code calls out to the xfrm state code to get
> those pointers when we could get it in an easier way via the state
> itself.
> 
> This patch adds an xfrm_state_afinfo to xfrm_mode (since they're
> address-specific) and changes the policy code to use it.  I've also
> added an owner field to do reference counting on the module providing
> the afinfo even though it isn't strictly necessary today since IPv6
> can't be unloaded yet.
> 
> Signed-off-by: Herbert Xu <herbert@...dor.apana.org.au>

Applied.

Thanks for doing this, those afinfo get/put things all over
the place really bugged me.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html