Ticket #429 (new defect)

Opened 11 months ago

Last modified 11 months ago

GLSV service reports Deadlock and CPU shoots up

Reported by: umesh.patel@… Owned by:
Priority: blocker Milestone: PL 2.0.2
Component: GLSv Version: 2.0.0
Keywords: Cc: kunal.kabra@…
patch waiting for maintainer: no

Description

GLSV service reports deadlock when thread takes locks in an EX mode using saLckResourceLock API. When two threads from the same process tried to take lock on same resource in EX mode, GLSV report Deadlock. CPU for ncs_glnd shoots up to 80%.

Please note that thread takes lock on only one resource. There is no execution path for a thread where it can hold lock one resource and tries for lock on another resource(which might have true deadlock condition).

Attachments

main_load.cpp (3.2 kB) - added by umesh.patel@… 11 months ago.
stub where threads take locks in EX mode
RtLockService.cpp (15.7 kB) - added by umesh.patel@… 11 months ago.
source code for wrapper class on lock service
RtLockService.hpp (1.9 kB) - added by umesh.patel@… 11 months ago.
interface for wrapper class on lock service

Change History

Changed 11 months ago by umesh.patel@…

stub where threads take locks in EX mode

Changed 11 months ago by umesh.patel@…

source code for wrapper class on lock service

Changed 11 months ago by umesh.patel@…

interface for wrapper class on lock service

Changed 11 months ago by umesh.patel@…

This is a very urgent requirement for our implementation and we are heldup from quite some time because of this issue. Request an immediate look into this problem

Changed 11 months ago by marioa

  • milestone changed from 3.0.0-M3 to PL 2.0.2

Add/Change #429 (GLSV service reports Deadlock and CPU shoots up)

Author



Action
as new
Note: See TracTickets for help on using tickets.