From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Kouya Shimura <kouya@jp.fujitsu.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/hotplug: fix locking
Date: Wed, 13 Jun 2012 04:16:57 -0400 [thread overview]
Message-ID: <4FD84C79.1000707@oracle.com> (raw)
In-Reply-To: <1339575111.24104.125.camel@zakaz.uk.xensource.com>
On 06/13/2012 04:11 AM, Ian Campbell wrote:
> On Mon, 2012-06-11 at 14:59 +0100, Zhigang Wang wrote:
>> This patch removes the ownner support and fixed this issue per my test.
> I think the changelog here needs to go into a bit more detail about why
> it is correct to remove the owner support. e.g. why is it no longer
> needed or why is it bogus. Also why does removing it fix the issue?
> Please describe the logic behind the change not just its impact on your
> test case.
Thanks Kouya for the info about Red Hat implement. I also like the flock
implement better.
My plan is to withdraw this patch and test Red Hat implement and if it works
fine, then I will submit the Red Hat patch (as far as it's GPL).
Thanks,
Zhigang
>
>> Kouya: would you please help to confirm this fix is correct?
>>
>> Anyone has encountered this issue please help to test.
>>
>> Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com>
>> Cc: Kouya Shimura <kouya@jp.fujitsu.com>
>>
>> diff -r 32034d1914a6 -r eb72d7090b59 tools/hotplug/Linux/locking.sh
>> --- a/tools/hotplug/Linux/locking.sh Thu Jun 07 19:46:57 2012 +0100
>> +++ b/tools/hotplug/Linux/locking.sh Mon Jun 11 09:29:43 2012 -0400
>> @@ -48,32 +48,14 @@ sigerr() {
>> _claim_lock()
>> {
>> local lockdir="$1"
>> - local owner=$(_lock_owner "$lockdir")
>> local retries=0
>>
>> while [ $retries -lt $LOCK_RETRIES ]
>> do
>> - mkdir "$lockdir" 2>/dev/null && trap "_release_lock $lockdir; sigerr" ERR &&
>> - _update_lock_info "$lockdir" && return
>> -
>> - local new_owner=$(_lock_owner "$lockdir")
>> - if [ "$new_owner" != "$owner" ]
>> - then
>> - owner="$new_owner"
>> - retries=0
>> - else
>> - local pid=$(echo $owner | cut -d : -f 1)
>> - if [ -n "$pid" -a "$pid" != "unknown" -a ! -f "/proc/$pid/status" ]
>> - then
>> - _release_lock $lockdir
>> - fi
>> - fi
>> -
>> + mkdir "$lockdir" 2>/dev/null && trap "_release_lock $lockdir; sigerr" ERR && return
>> if [ $retries -gt $LOCK_SPINNING_RETRIES ]
>> then
>> sleep $LOCK_SLEEPTIME
>> - else
>> - sleep 0
>> fi
>> retries=$(($retries + 1))
>> done
>> @@ -91,20 +73,7 @@ _release_lock()
>> _steal_lock()
>> {
>> local lockdir="$1"
>> - local owner=$(cat "$lockdir/owner" 2>/dev/null || echo "unknown")
>> - log err "Forced to steal lock on $lockdir from $owner!"
>> + log err "Forced to steal lock on $lockdir!"
>> _release_lock "$lockdir"
>> _claim_lock "$lockdir"
>> }
>> -
>> -
>> -_lock_owner()
>> -{
>> - cat "$1/owner" 2>/dev/null || echo "unknown"
>> -}
>> -
>> -
>> -_update_lock_info()
>> -{
>> - echo "$$: $0" >"$1/owner"
>> -}
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2012-06-13 8:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 13:59 [PATCH] tools/hotplug: fix locking Zhigang Wang
2012-06-12 6:53 ` Kouya Shimura
2012-06-13 2:25 ` Marek Marczykowski
2012-06-13 8:11 ` Ian Campbell
2012-06-13 8:16 ` Zhigang Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-13 17:29 Zhigang Wang
2012-06-20 15:34 ` Ian Campbell
2012-06-20 17:53 ` Zhigang Wang
2012-06-21 11:42 ` Ian Campbell
2012-06-21 11:49 ` Ian Campbell
2012-06-21 12:08 ` Zhigang Wang
2012-06-21 12:23 ` Daniel P. Berrange
2012-06-21 13:07 ` Zhigang Wang
2012-06-21 12:20 ` Daniel P. Berrange
2012-06-26 15:53 ` Ian Campbell
2012-06-26 16:14 ` Daniel P. Berrange
2012-07-04 14:48 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD84C79.1000707@oracle.com \
--to=zhigang.x.wang@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=kouya@jp.fujitsu.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).