On Mon, Jun 05, 2017 at 11:39:14AM +0200, Martin Pieuchot wrote:
> On 30/05/17(Tue) 14:05, Claudio Jeker wrote:
> > This is more or less the same thing for PF_KEY that we now do in PF_ROUTE.
> > Use one PCB LIST on the keycb and embedd the rawcb in that PF_KEY cb.
> > Diff also has a few variable r
On 30/05/17(Tue) 14:05, Claudio Jeker wrote:
> This is more or less the same thing for PF_KEY that we now do in PF_ROUTE.
> Use one PCB LIST on the keycb and embedd the rawcb in that PF_KEY cb.
> Diff also has a few variable renames in it to make this code less alien
> regarding the rest of our ker
This is more or less the same thing for PF_KEY that we now do in PF_ROUTE.
Use one PCB LIST on the keycb and embedd the rawcb in that PF_KEY cb.
Diff also has a few variable renames in it to make this code less alien
regarding the rest of our kernel. Mainly use so instead of socket and
pfkeyv2_sock
