Hi Dave/Chris,
Thanks for the pointers. I am able to see Coverity defects now. My reason for
looking for Coverity logs is following
It has recently been came to my notice that vnet APIs and their caller do not
free clib_error_t * properly. Usage of vnet_[sw|hw]_interface_set_flags() APIs
are w
It looks like vpp is crashing while expiring timers from the main thread
process timer wheel. That’s not been reported before.
You might want to dust off .../extras/deprecated/vlib/unix/cj.[ch], and make a
circular log of timer pool_put operations to work out what’s happening.
D.
From: vpp-dev
Hi,
The thing that caused me the most headaches is the validity of the timer
handler. When a timer is expired, its handle becomes invalid and any
attempt to use it will cause havoc.
This can be a real problem when you try to cancel timers from within the
expire handler of another timer. You can no
Thanks Dave for the quick analysis. Are there some Debug CLIs that I can
run to analyse?
We are not using the VPP timers as we have our own timer library. In VPP,
we have added a couple of VPP nodes(process, internal and input). Could
these be causing the problem?
Thanks,
Rajith
On Wed, Sep 2, 20
Given the amount of soak-time / perf/scale / stress testing which the tw_timer
code has experienced, it’s reasonably likely that your application is
responsible.
Caution is required when dealing with timers other than the timer which has
expired.
If you have > 1 timer per object and you manipu
Known Coverity UI bug. Happens all the time for me.
Back up one page, and click on "show me the bugs" again. It should work.
D.
From: vpp-dev@lists.fd.io On Behalf Of Nitin Saxena
Sent: Wednesday, September 2, 2020 3:31 AM
To: vpp-dev
Subject: [vpp-dev] How to see coverity logs
Hi Maintainers
Oh, I think I worked out what you mean; you authorized Coverity to use GitHub
as an authenticator, and in the process gave Coverity access to every Git
repository you have access to? I refuse it that access every time it asks.
That should not have an impact on your access to the defects of VPP,
Hi all,
Just a kind reminder that from tomorrow until we pull the stable/2009 branch on
Wednesday 9th September, we will avoid submitting the API changes and risky
commits.
(The wireguard plugin gets a one-off waiver with a deadline of Tuesday, since
it’s a separate new plugin being added, so
The correct URL is https://scan.coverity.com/projects/fd-io-vpp (you missed a
trailing p) but I am not sure how you would add it "to your github". It's just
a web page.
I also note that you're listed as a contributor, so you should have access to
see the defects.
Chris.
From: vpp-dev@lists.fd
> Is there anyone trying to run openvpn on VPP?
Not that I am aware of, there is on-going work on wireguard however:
https://gerrit.fd.io/r/c/vpp/+/27963
> Or how to develop an Openvpn feature on the VPP?
You should develop a plugin. You can look at VPP doc and sample plugin
https://fd.io/docs
Hi Maintainers,
I would like to see coverity logs for latest VPP build. I tried adding
https://scan.coverity.com/projects/fd-io-vp to my github but when I click on
"View Defects" it says "Permission denied".
Is it possible to view coverity logs or I am missing anything?
Thanks,
Nitin
-=-=-=-=
Hi experts,
We encounterd crash when configured nat with gre interface
version : vpp master
vpp configuration:
G0 ip 192.168.102.151
create gre tunnel src 192.168.102.151 dst 192.168.100.174
set interface stat gre0 up
set interface ip addr gre0 8.8.8.1/30
*set interface nat44 out gre0 output-feat
12 matches
Mail list logo
