Racoon and setkey problems

[Misak Khachatryan]

Here is the result:

# dtrace -s key.d
dtrace: script 'key.d' matched 8 probes
CPU     ID                    FUNCTION:NAME
 3  25400                  soreserve:entry 32768 65536
 7  25400                  soreserve:entry 8192 8192
 7   7957                key_attach:return 0
 7  12872              sbappendaddr:return 1
             kernel`key_sendup0+0xee
             kernel`key_sendup_mbuf+0x14b
             kernel`key_parse+0x87f

 7   7969               key_sendup0:return 0
             kernel`key_sendup_mbuf+0x14b
             kernel`key_parse+0x87f
             kernel`sosend_generic+0x476

 7  12872              sbappendaddr:return 0
             kernel`key_sendup0+0xee
             kernel`key_sendup_mbuf+0x1e6
             kernel`key_parse+0x87f

 7   7969               key_sendup0:return 55
             kernel`key_sendup_mbuf+0x1e6
             kernel`key_parse+0x87f
             kernel`sosend_generic+0x476

 7  24402           key_sendup_mbuf:return 55
             kernel`key_parse+0x87f
             kernel`sosend_generic+0x476
             kernel`kern_sendit+0x245

 7  11197                 key_parse:return 55


^C

Best regards,
Misak Khachatryan


On Thu, Feb 22, 2018 at 5:11 PM, Andrey V. Elsukov <bu7cher at yandex.ru> wrote:
> On 22.02.2018 15:13, Misak Khachatryan wrote:
>> I did this way:
>>
>> # dtrace -s key.d
>> dtrace: script 'key.d' matched 6 probes
>> CPU     ID                    FUNCTION:NAME
>>  7   7957                key_attach:return 0
>>  7   7969               key_sendup0:return 0
>>  7   7969               key_sendup0:return 55
>>  7  24402           key_sendup_mbuf:return 55
>>  7  11197                 key_parse:return 55
>> ^C
>
> Ok, I updated the script, please, show new result
>
> --
> WBR, Andrey V. Elsukov