Hi Carlito,
The standard bug reporting practice is documented on the wiki [0].
Alternatively, run your debug version of VPP in gdb and report the
backtrace when vpp crashes.
Thanks,
-daw-
[0] https://wiki.fd.io/view/VPP/BugReports
On 8/16/2019 11:12 PM, carlito nueno wrote:
Hi Dave,
Thanks for the patch. I merged your edits and compiled a debug version
using stable/1908 as base.
Every time a make a ping request from a LAN device, VPP is restarting.
Sometimes vppctl just hangs, but when I do get into vppctl, if I run a
command (ex: sh nat44 address), VPP again restarts.
I know this information is not that helpful. Please let me know what
information you need and, I can also run more tests.
Thanks!
On Thu, Aug 15, 2019 at 12:20 PM Dave Barach via Lists.Fd.Io
<dbarach=cisco....@lists.fd.io> wrote:
See https://jira.fd.io/browse/VPP-1746, and
https://gerrit.fd.io/r/c/vpp/+/21338 which fixes gross non-operation of the
name resolver.
Process created on demand, with node index in the main_t. Needed to remove the
static vlib_node_registration_t and use dm->resolver_process_node_index vs.
unused_mumble_registration.node_index.
Passing 0 when signaling name resolution events couldn’t possibly work.
D.
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Dave Barach via
Lists.Fd.Io
Sent: Thursday, August 15, 2019 2:54 PM
To: anoopnairh...@gmail.com; vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Crash when using dns_name_server
Folks,
I’ll look at these issues. It would be helpful if people would contribute
patches, or at least write Jira tickets. If we don’t know it’s broken, it won’t
get fixed...
To level-set: the DNS name resolver has been lightly used. Nothing would
surprise me at this point.
D.
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of
anoopnairh...@gmail.com
Sent: Thursday, August 15, 2019 1:07 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Crash when using dns_name_server
Hi Carlio,
I had faced a similar crash with DNS module while resolving names.
The dns_cache_lock is in locked state after initialization. Because of this the first
worker thread which attempts to take this lock will find it in "locked" state
and spin forever. So the main thread panics when it tries for barrier sync. Attached the
patch which solved my problem
I could find couple of other issues in the DNS module and the patch has the fix
for them as well.
- DNS lock is not released while processing dns request -> causes deadlock
- resolve a name from VAT when there is no server configured -> crash due
to a NULL pointer deference
- delete_random_entry() is invoked while holding DNS lock -> a potential
deadlock
Please check if it helps you.
thanks
Anoop
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13754): https://lists.fd.io/g/vpp-dev/message/13754
Mute This Topic: https://lists.fd.io/mt/32881233/675621
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [carlitonu...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13771): https://lists.fd.io/g/vpp-dev/message/13771
Mute This Topic: https://lists.fd.io/mt/32881233/675079
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [dwallac...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13777): https://lists.fd.io/g/vpp-dev/message/13777
Mute This Topic: https://lists.fd.io/mt/32881233/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
