pbb_evpn: [4.0.0.0-3044~kilo] vRouter crash observed @free_pipe_info+0x62/0xa0, put_pipe_info+0x44/0x60 with continuous vmi/bd addition/deletion
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.0 |
In Progress
|
High
|
Divakar Dharanalakota | |||
R2.1 |
In Progress
|
High
|
Divakar Dharanalakota | |||
R2.20 |
Fix Committed
|
High
|
Divakar Dharanalakota | |||
R2.21.x |
Fix Committed
|
High
|
Divakar Dharanalakota | |||
R2.22.x |
Fix Committed
|
High
|
Divakar Dharanalakota | |||
R3.0 |
Fix Committed
|
High
|
Divakar Dharanalakota | |||
R3.1 |
Fix Committed
|
High
|
Divakar Dharanalakota | |||
R3.2 |
Fix Committed
|
High
|
Divakar Dharanalakota | |||
Trunk |
Fix Committed
|
High
|
Divakar Dharanalakota |
Bug Description
vRouter crash observed @free_pipe_
[682731.189946] Call Trace:
[682731.200674] [<ffffffff811cb
[682731.211419] [<ffffffff811cb
[682731.221761] [<ffffffff811cb
[682731.231997] [<ffffffff811c4
[682731.242247] [<ffffffff811c4
[682731.252178] [<ffffffff8108b
[682731.262296] [<ffffffff81014
[682731.271868] [<ffffffff8173e
[682731.281511] Code: Bad RIP value.
[682731.290846] RIP [< (null)>] (null)
[682731.300142] RSP <ffff8800c97bfe38>
[682731.309062] CR2: 0000000000000000
Core file is copied to:
bhushana@
Reviewed: https:/
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: master
commit 0b81b2bbd7dc50a
Author: Divakar D <email address hidden>
Date: Thu Mar 23 12:06:39 2017 +0530
Increment Nexthop ref count atomically
Right now, the NH's refcount is not incremented atomically as reference
to NH is always taken from a single thread in nelink context. This is
becuase Routes, Labels, and other NH's access an NH only when Agent
performs config changes. But with data path mac learning in place
because of PBB, reference to NH, esp L2 Mutlicast NH, happens from
multiple threads leading to requirement incrementing it atomically. Not
doing it causes the ref count to go bad for that particular NH and
results in double free of NH.
Change-Id: I0afa517b56eeac
closes-bug: #1672293
closes-bug: #1672373
closes-bug: #1673663
Review in progress for https:/
Submitter: Divakar Dharanalakota (<email address hidden>)
Review in progress for https:/
Submitter: Divakar Dharanalakota (<email address hidden>)
Review in progress for https:/
Submitter: Divakar Dharanalakota (<email address hidden>)
Review in progress for https:/
Submitter: Divakar Dharanalakota (<email address hidden>)
Review in progress for https:/
Submitter: Divakar Dharanalakota (<email address hidden>)
Review in progress for https:/
Submitter: Divakar Dharanalakota (<email address hidden>)
Review in progress for https:/
Submitter: Divakar Dharanalakota (<email address hidden>)
Reviewed: https:/
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R3.1
commit 0cfe6339fa3d2de
Author: Divakar D <email address hidden>
Date: Thu Mar 23 12:06:39 2017 +0530
Increment Nexthop ref count atomically
Right now, the NH's refcount is not incremented atomically as reference
to NH is always taken from a single thread in nelink context. This is
becuase Routes, Labels, and other NH's access an NH only when Agent
performs config changes. But with data path mac learning in place
because of PBB, reference to NH, esp L2 Mutlicast NH, happens from
multiple threads leading to requirement incrementing it atomically. Not
doing it causes the ref count to go bad for that particular NH and
results in double free of NH.
Change-Id: I0afa517b56eeac
closes-bug: #1672293
closes-bug: #1672373
closes-bug: #1673663
OpenContrail Admin (ci-admin-f) wrote : | #19 |
Reviewed: https:/
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R3.0
commit 9900fb6ecc25348
Author: Divakar D <email address hidden>
Date: Thu Mar 23 12:06:39 2017 +0530
Increment Nexthop ref count atomically
Right now, the NH's refcount is not incremented atomically as reference
to NH is always taken from a single thread in nelink context. This is
becuase Routes, Labels, and other NH's access an NH only when Agent
performs config changes. But with data path mac learning in place
because of PBB, reference to NH, esp L2 Mutlicast NH, happens from
multiple threads leading to requirement incrementing it atomically. Not
doing it causes the ref count to go bad for that particular NH and
results in double free of NH.
Change-Id: I0afa517b56eeac
closes-bug: #1672293
closes-bug: #1672373
closes-bug: #1673663
OpenContrail Admin (ci-admin-f) wrote : | #20 |
Reviewed: https:/
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R3.2
commit d0eeccc9ec0cbe1
Author: Divakar D <email address hidden>
Date: Thu Mar 23 12:06:39 2017 +0530
Increment Nexthop ref count atomically
Right now, the NH's refcount is not incremented atomically as reference
to NH is always taken from a single thread in nelink context. This is
becuase Routes, Labels, and other NH's access an NH only when Agent
performs config changes. But with data path mac learning in place
because of PBB, reference to NH, esp L2 Mutlicast NH, happens from
multiple threads leading to requirement incrementing it atomically. Not
doing it causes the ref count to go bad for that particular NH and
results in double free of NH.
Change-Id: I0afa517b56eeac
closes-bug: #1672293
closes-bug: #1672373
closes-bug: #1673663
tags: | added: crashes |
information type: | Proprietary → Public |
OpenContrail Admin (ci-admin-f) wrote : | #21 |
Reviewed: https:/
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R2.21.x
commit e20b49b09e4227f
Author: Divakar D <email address hidden>
Date: Thu Mar 23 12:06:39 2017 +0530
Increment Nexthop ref count atomically
Right now, the NH's refcount is not incremented atomically as reference
to NH is always taken from a single thread in nelink context. This is
becuase Routes, Labels, and other NH's access an NH only when Agent
performs config changes. But with data path mac learning in place
because of PBB, reference to NH, esp L2 Mutlicast NH, happens from
multiple threads leading to requirement incrementing it atomically. Not
doing it causes the ref count to go bad for that particular NH and
results in double free of NH.
Change-Id: I0afa517b56eeac
closes-bug: #1672293
closes-bug: #1672373
closes-bug: #1673663
Review in progress for https:/
Submitter: Divakar Dharanalakota (<email address hidden>)
Reviewed: https:/
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R2.20
commit 72daf05792561fb
Author: Divakar D <email address hidden>
Date: Thu Mar 23 12:06:39 2017 +0530
Increment Nexthop ref count atomically
Right now, the NH's refcount is not incremented atomically as reference
to NH is always taken from a single thread in nelink context. This is
becuase Routes, Labels, and other NH's access an NH only when Agent
performs config changes. But with data path mac learning in place
because of PBB, reference to NH, esp L2 Mutlicast NH, happens from
multiple threads leading to requirement incrementing it atomically. Not
doing it causes the ref count to go bad for that particular NH and
results in double free of NH.
Change-Id: I0afa517b56eeac
closes-bug: #1672293
closes-bug: #1672373
closes-bug: #1673663
OpenContrail Admin (ci-admin-f) wrote : | #25 |
Reviewed: https:/
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R2.22.x
commit 1f01b6f0dab4858
Author: Divakar D <email address hidden>
Date: Thu Mar 23 12:06:39 2017 +0530
Increment Nexthop ref count atomically
Right now, the NH's refcount is not incremented atomically as reference
to NH is always taken from a single thread in nelink context. This is
becuase Routes, Labels, and other NH's access an NH only when Agent
performs config changes. But with data path mac learning in place
because of PBB, reference to NH, esp L2 Mutlicast NH, happens from
multiple threads leading to requirement incrementing it atomically. Not
doing it causes the ref count to go bad for that particular NH and
results in double free of NH.
Change-Id: I0afa517b56eeac
closes-bug: #1672293
closes-bug: #1672373
closes-bug: #1673663
Review in progress for https:/ /review. opencontrail. org/29831
Submitter: Divakar Dharanalakota (<email address hidden>)