From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Zhigang Wang <zhigang.x.wang@oracle.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [xen-unstable test] 13461: regressions - FAIL
Date: Thu, 5 Jul 2012 11:57:36 +0100 [thread overview]
Message-ID: <20120705105736.GH13884@redhat.com> (raw)
In-Reply-To: <20469.29270.801506.115753@mariner.uk.xensource.com>
On Thu, Jul 05, 2012 at 11:54:14AM +0100, Ian Jackson wrote:
> Daniel P. Berrange writes ("Re: [Xen-devel] [xen-unstable test] 13461: regressions - FAIL"):
> > On Thu, Jul 05, 2012 at 11:40:04AM +0100, Ian Jackson wrote:
> > > release_lock()
> > > {
> > > _setlockfd $1
> > > - flock -u $_lockfd
> > > + rm "$_lockfile"
> >
> > I think you still want the 'flock' line here, but have it after the
> > 'rm' line. Otherwise you leave the $_lockfd filehandle open. Yes,
> > I know the calling script will probably just exit, but it doesn't
> > hurt to be careful here.
>
> flock -u won't close the fd. If that's what you want then we would
> have to do so explicitly.
>
> But, in the meantime the old lockfile exists and is pointlessly
> flocked but is unlinked, which is harmless apart from being a slight
> resource leak.
>
> Note that anyone who inherits a the fd from the hotplug script will
> end up keeping the file in existence, so closing it here (with or
> without unlocking it) may not do any good. And if there are no such
> children with a copy of the fd then when the hotplug script dies or
> exits the stale lockfile will be reaped by the kernel.
>
> So I think it's fine as it is.
Ok, agreed.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-07-05 10:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 4:23 [xen-unstable test] 13461: regressions - FAIL xen.org
2012-07-05 5:49 ` Ian Campbell
2012-07-05 9:28 ` Daniel P. Berrange
2012-07-05 9:31 ` Ian Campbell
2012-07-05 10:40 ` Ian Jackson
2012-07-05 10:46 ` Daniel P. Berrange
2012-07-05 10:54 ` Ian Jackson
2012-07-05 10:57 ` Daniel P. Berrange [this message]
2012-07-05 10:57 ` Ian Campbell
2012-07-05 11:00 ` Roger Pau Monne
2012-07-05 11:03 ` Ian Campbell
2012-07-05 11:21 ` Ian Jackson
2012-07-05 11:32 ` Ian Campbell
2012-07-05 11:34 ` Ian Campbell
2012-07-05 11:43 ` [xen-unstable test] 13461: regressions - FAIL [and 1 more messages] Ian Jackson
2012-07-05 11:53 ` [xen-unstable test] 13461: regressions - FAIL Roger Pau Monne
2012-07-05 11:57 ` 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=20120705105736.GH13884@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=zhigang.x.wang@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.