> It seems the issue arose due to changes in the DPDK read-write lock
> implementation. Following these changes, the RW-lock no longer supports
> recursion, implying that a single thread shouldn't obtain a read lock if it
> already possesses one. The problem arises during initialization: the
> rt
https://bugs.dpdk.org/show_bug.cgi?id=1277
Bug ID: 1277
Summary: memory_hotplug_lock deadlock during initialization
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: no
2 matches
Mail list logo