Thanks, glad to hear it... D.
From: Rajith PR
Sent: Wednesday, June 10, 2020 4:04 AM
To: Dave Barach (dbarach)
Cc: Benoit Ganne (bganne) ; vpp-dev ;
Neale Ranns (nranns)
Subject: Re: [vpp-dev] SEGMENTATION FAULT in load_balance_get()
Hi Dave,
We ran a good number of scale tests with the fix
iginal Message-
> From: vpp-dev@lists.fd.io On Behalf Of Dave Barach
> via lists.fd.io
> Sent: Wednesday, June 3, 2020 7:08 AM
> To: Benoit Ganne (bganne) ; raj...@rtbrick.com
> Cc: vpp-dev ; Neale Ranns (nranns)
> Subject: Re: [vpp-dev] SEGMENTATION FAULT in load_balance_get()
: Re: [vpp-dev] SEGMENTATION FAULT in load_balance_get()
+1, can't tell which poison pattern is involved without a scorecard.
load_balance_alloc_i (...) is clearly not thread-safe due to calls to
pool_get_aligned (...) and vlib_validate_combined_counter(...).
Judicious u
ave Barach (dbarach)
Cc: vpp-dev ; Neale Ranns (nranns)
Subject: RE: [vpp-dev] SEGMENTATION FAULT in load_balance_get()
Neale is away and might be slow to react.
I suspect the issue is when creating new load balance entry through
load_blance_create(), which will get a new element from the load balance p
PR via
> lists.fd.io
> Sent: mercredi 3 juin 2020 05:46
> To: Dave Barach (dbarach)
> Cc: vpp-dev ; Neale Ranns (nranns)
> Subject: Re: [vpp-dev] SEGMENTATION FAULT in load_balance_get()
>
> Hi Dave/Neal,
>
> The adj_poison seems to be a filling pattern - - 0xfefe. Am I lookin
ern –
> copying Neale for an opinion.
>
>
>
> D.
>
>
>
> *From:* vpp-dev@lists.fd.io *On Behalf Of *Rajith
> PR via lists.fd.io
> *Sent:* Tuesday, June 2, 2020 10:00 AM
> *To:* vpp-dev
> *Subject:* [vpp-dev] SEGMENTATION FAULT in load_balance_get()
>
>
The code manages to access a poisoned adjacency – 0x131313 fill pattern –
copying Neale for an opinion.
D.
From: vpp-dev@lists.fd.io On Behalf Of Rajith PR via
lists.fd.io
Sent: Tuesday, June 2, 2020 10:00 AM
To: vpp-dev
Subject: [vpp-dev] SEGMENTATION FAULT in load_balance_get()
Hello All
Hello All,
In *19.08** VPP version* we are seeing a crash while accessing the
*load_balance_pool* in *load_balanc_get*() function. This is happening
after *enabling worker threads*.
As such the FIB programming is happening in the main thread and in one of
the worker threads we see this crash.
Als
