From: Ian Campbell <Ian.Campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] hotplug/Linux: close lockfd after lock attempt
Date: Mon, 15 Oct 2012 09:01:05 +0100 [thread overview]
Message-ID: <1350288065.14440.5.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <20121013223558.GA19665@aepfle.de>
On Sat, 2012-10-13 at 23:35 +0100, Olaf Hering wrote:
> On Sat, Oct 13, Olaf Hering wrote:
>
> > hotplug/Linux: close lockfd after lock attempt
> >
> > When a HVM guest is shutdown some of the 'remove' events can not claim
> > the lock for some reason. Instead they try to grab the lock in a busy
> > loop, until udev reaps the xen-hotplug-cleanup helper.
> > After analyzing the resulting logfile its not obvious what the cause is.
> > The only explanation is that bash (?) gets confused if the same lockfd
> > is opened again and again. Closing it in each iteration seem to fix the
> > issue.
>
> Can be reproduced with this testcase on sles11sp2, not on openSuSE 11.4:
So this is a bash bug? Have you reported it against bash?
Ian.
>
> # cat test.sh
> set -x
> source locking.sh
>
> l=lock
> claim_lock $l
> sleep 1
> release_lock $l
>
>
> # bash test.sh & bash test.sh & bash test.sh & bash test.sh &
>
>
> Olaf
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-10-15 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 15:59 [PATCH] hotplug/Linux: close lockfd after lock attempt Olaf Hering
2012-10-13 22:35 ` Olaf Hering
2012-10-15 8:01 ` Ian Campbell [this message]
2012-10-15 8:42 ` Olaf Hering
2012-10-18 8:35 ` 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=1350288065.14440.5.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=olaf@aepfle.de \
--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).