| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 1128] New: context inappropriate connection sharing logic incomplete |
| From: | bugzilla-daemon@xxxxxxxxxxx |
| Date: | Tue, 24 Nov 2015 15:44:06 +0000 |
| Auto-submitted: | auto-generated |
| Delivered-to: | pcp@xxxxxxxxxxx |
Connection sharing protections in commit ec7da652c etc. does not do a complete job: it ignores that pmDupContext and subsequent pmStore container-changing on one copy will affect both clients. Similarly, two container-less pmNewContexts, one of which gets a container-changing pmstore. Problem found by inspection. Indirectly confirmable by number of connections / pmcd.client tuples associated with such an application: just 1. http://oss.sgi.com/pipermail/pcp/2015-October/008595.html PS. The pmcd.client* metrics should be documented with respect to their peculiar pmStore semantics (incoming instance#s ignored & redirected to the current client, which makes sense because the instance numbers aren't meaningful to pmapi clients in the first place). You are receiving this mail because:
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 1256125] SELinux is preventing /usr/bin/pmlogger from 'open' accesses on the file /var/lib/pcp/config/pmlogger/config.default., bugzilla |
|---|---|
| Next by Date: | [Bug 1284417] Python PMAPI pmSetMode does not allow None timeval, bugzilla |
| Previous by Thread: | [Bug 1127] New: document connection sharing OR remove PM_CTXFLAG_EXCLUSIVE, bugzilla-daemon |
| Next by Thread: | [Bug 1129] New: pmDupContext-created context SEGVs during pmDestroyContext, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |