On 3 August 2017 at 14:34, Ben Pfaff wrote:
> On Mon, Jul 31, 2017 at 04:54:21PM -0700, Joe Stringer wrote:
>> This calls is operating on messages generated by the datapath. If a
>> datapath implementation sends improperly formatted netlink attributes,
>> then it's possible for a revalidator threa
On 2 August 2017 at 17:11, Greg Rose wrote:
> On 07/31/2017 04:54 PM, Joe Stringer wrote:
>>
>> This calls is operating on messages generated by the datapath. If a
>
>
> s/calls/call
>
>> datapath implementation sends improperly formatted netlink attributes,
>> then it's possible for a revalidator
On Mon, Jul 31, 2017 at 04:54:21PM -0700, Joe Stringer wrote:
> This calls is operating on messages generated by the datapath. If a
> datapath implementation sends improperly formatted netlink attributes,
> then it's possible for a revalidator thread to end up trapped in an
> infinite loop iteratin
On 07/31/2017 04:54 PM, Joe Stringer wrote:
This calls is operating on messages generated by the datapath. If a
s/calls/call
datapath implementation sends improperly formatted netlink attributes,
then it's possible for a revalidator thread to end up trapped in an
infinite loop iterating acros
This calls is operating on messages generated by the datapath. If a
datapath implementation sends improperly formatted netlink attributes,
then it's possible for a revalidator thread to end up trapped in an
infinite loop iterating across the actions attributes. Rather than using
the UNSAFE variatio
