When attempting to build vpp against system libraries (dpdk, libbpf, etc)
on Debian Bullseye I get the following error when building the
af_xdp_plugin.so
Is the af_xdp plugin doing something unusual with libbpf?
Thanks,
Nick
cd vpp/src
mkdir mybuild
cd mybuild
cmake -GNinja
Thanks Benoit.
Actually Same out of tree plugins are working fine with SANITIZER Enabled
on vpp 2101.
Will update the result with the patch provided by you and test which
Florin suggested .
Thanks & Regards,
Chetan
On Wed, Sep 8, 2021 at 8:13 PM Benoit Ganne (bganne)
wrote:
> Here is maybe a
Here is maybe a better fix: https://gerrit.fd.io/r/c/vpp/+/33693
My previous changeset was only hiding the underlying issue which is arrays
passed to vlib_buffer_enqueue_to_next() must be big enough to allow for some
overflow (because of the use of clib_mask_compare_u16() and
Hi Venky,
Which nodes get called depends on the nature of the route. Take this trivial
example
DBGvpp# set int state loop0 up
DBGvpp# set int ip addr loop0 10.0.0.1/24
This route is non recursive
DBGvpp# ip route 1.1.1.1/32 via 10.0.0.2 loop0
This one is recursive
DBGvpp# ip route
Prashant,
> Thanks for the feedback.
> Out of curiosity, what is the motivation of this contract about
> minimal length of chained buffer data -- surely, my case being in
> point, the chaining framework should not make any assumptions about
> how the user would use it.
There are lots of features
It is mainly about first segment. Majority of vpp code asumes that packet
headers are in the first segment. This is to prevent crashes due to headers
being split between 2.
—
Damjan
> On 08.09.2021., at 11:31, Prashant Upadhyaya wrote:
>
> Hi Damjan,
>
> Thanks for the feedback.
> Out of
Hi Damjan,
Thanks for the feedback.
Out of curiosity, what is the motivation of this contract about
minimal length of chained buffer data -- surely, my case being in
point, the chaining framework should not make any assumptions about
how the user would use it.
Regards
-Prashant
On Tue, Sep 7,
Hi Chetan,
Something like the following should exercise using iperf and homegrown test
apps most of the components of the host stack, i.e., vcl, session layer and the
transports, including tcp:
make test-debug VPP_EXTRA_CMAKE_ARGS=-DVPP_ENABLE_SANITIZE_ADDR=ON CC=gcc-10
TEST=vcl
