pcp
[Top] [All Lists]

Re: [pcp] libpcp: unlock context before returning (#50)

To: performancecopilot/pcp <pcp@xxxxxxxxxxxxxxxxxx>
Subject: Re: [pcp] libpcp: unlock context before returning (#50)
From: Ken McDonell <notifications@xxxxxxxxxx>
Date: Mon, 09 Nov 2015 11:34:40 -0800
Delivered-to: pcp@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=github.com; h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Hp+/I7iZMnjKsnXW/wpg77juoh4=; b=s1mOjRrdxv6ulFk/ rRi+tv8Pb1wV9vC79sQs/NgOw2sEJ7Iw/N+VdjRChv2EFvxUifWC7TQYiwbnmYMn U1DxrukkLD1+djGhaqSA1WKWnfXpIsNfOOrv0O3RJF8lQDUEk89yFGbLlj7T7/yd f4FIVBs8r66Jca3kPqlz+w7mMa4=
In-reply-to: <performancecopilot/pcp/pull/50@xxxxxxxxxx>
List-archive: https://github.com/performancecopilot/pcp
List-id: performancecopilot/pcp <pcp.performancecopilot.github.com>
List-post: <mailto:reply+00bd08b66428e3bfc748d17cd17ac9fc9ad40237f36d21cf92cf000000011258b75092a169ce06e7914e@reply.github.com>
List-unsubscribe: <mailto:unsub+00bd08b66428e3bfc748d17cd17ac9fc9ad40237f36d21cf92cf000000011258b75092a169ce06e7914e@reply.github.com>, <https://github.com/notifications/unsubscribe/AL0ItvSZyWrGuqx6OUQ7inpWKthLw5ZAks5pEOzQgaJpZM4GecmI>
References: <performancecopilot/pcp/pull/50@xxxxxxxxxx>
Reply-to: performancecopilot/pcp <reply+00bd08b66428e3bfc748d17cd17ac9fc9ad40237f36d21cf92cf000000011258b75092a169ce06e7914e@xxxxxxxxxxxxxxxx>

Looks good Ryan, thanks. I've pulled your commit into my tree and it will flow back to github via pcp.io in due course.

This is a pretty unlikely code path (calling pmGetArchiveLabel() when the current context is valid, but not an archive) and I would expect none of our code can actually be persuaded to do this, so I am curious if you actually observed the problem that this patch fixes, or noticed by code inspection, or have some devious test harness and lock audit tool that exposed the logic error.

Anyway, thanks for improving the correctness and robustness of the code.


Reply to this email directly or view it on GitHub.

<Prev in Thread] Current Thread [Next in Thread>