xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v1 02/10] libxl_internal: functions to lock / unlock domain configuration
Date: Fri, 25 Jul 2014 11:36:37 +0100	[thread overview]
Message-ID: <20140725103637.GI28444@zion.uk.xensource.com> (raw)
In-Reply-To: <21457.20298.555817.484254@mariner.uk.xensource.com>

On Thu, Jul 24, 2014 at 07:24:10PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH v1 02/10] libxl_internal: functions to lock / unlock domain configuration"):
> > Simple file lock taken from xl to serialise access to "libxl-json" file.
> > If a thread cannot get hold of the lock it waits due to F_SETLKW.
> 
> Right.
> 
> > In order to generate lock file name, rename userdata_path to
> > libxl__userdata_path and declare it in libxl_internal.h
> 
> I don't mind it in such a small patch but in general it is easier to
> review things if non-functional changes like this are split out into a
> separate patch.
> 

Ack.

> > +int libxl__lock_domain_configuration(libxl__gc *gc, uint32_t domid,
> > +                                     int *fd_lock)
> > +{
> ...
> > +    int rc;
> > +    struct flock fl;
> > +    const char *lockfile;
> > +
> > +    if (*fd_lock >= 0)
> > +        return ERROR_INVAL;
> 
> Why not assert() ?
> 

Ack.

> > +    lockfile = libxl__userdata_path(gc, domid, "libxl-json.lock", "d");
> 
> Perhaps lockfile = ...(, "libxl-json", "l") ?  I think users of
> libxl__userdata_path are entitled to invent their own `wh' values.
> 

Good to know.

> Otherwise you have to document "libxl-json.lock" as a reserved
> userdata name (which is a bit daft because no-one would use it, but it
> is, formally speaking, wrong to use it here).
> 

I think I will go with the "l" approach.

> > +    *fd_lock = open(lockfile, O_WRONLY|O_CREAT, S_IWUSR);
> > +    if (*fd_lock < 0) {
> > +        LOGE(ERROR, "cannot open lockfile %s errno=%d\n", lockfile, errno);
> 
> LOGE's message should not contain \n.
> 

Fixed.

> > +    if (fcntl(*fd_lock, F_SETFD, FD_CLOEXEC) < 0) {
> 
> What's wrong with libxl_fd_set_cloexec ?
> 

Will use this one.

This implementation was basically a copy of the one in xl, I didn't
check if there's some helper function to do that.

> > +        close(*fd_lock);
> 
> Please use the idempotent `goto out' error handling style to deal with
> closing the fd on error.  Your failure to do so has resulted in
> error-case fd leak in this function.
> 

Ack.

> > +get_lock:
> > +    fl.l_type = F_WRLCK;
> > +    fl.l_whence = SEEK_SET;
> > +    fl.l_start = 0;
> > +    fl.l_len = 0;
> > +    rc = fcntl(*fd_lock, F_SETLKW, &fl);
> > +    if (rc < 0 && errno == EINTR)
> > +        goto get_lock;
> 
> Please, no more of these `goto'-based loops!
> 

Ack.

> > +    if (rc < 0) {
> > +        LOGE(ERROR, "cannot acquire lock %s errno=%d\n", lockfile, errno);
> > +        rc = ERROR_FAIL;
> 
> goto out.
> 
> > +    } else
> > +        rc = 0;
> 
> No, not like that.  Like this:
> 
>      rc = 0;
>      return rc;
> 
>    out:
>      if (*fd_lock >= 0) { close(*fd_lock); *fd_lock = -1; }
>      return rc;
> 
> 

Will fix this.

> > +int libxl__unlock_domain_configuration(libxl__gc *gc, uint32_t domid,
> > +                                       int *fd_lock)
> > +{
> 
> Closing the fd is sufficient.  I'm not even sure why you need a whole
> function for this; the caller could just call close().  The caller can
> can ignore any errors (which I think are impossible anyway) since
> after close the fd is gone anyway.
> 
> > +/*
> > + * Lock / unlock domain configuration in libxl private data store.
> > + * fd_lock contains the file descriptor pointing to the lock file.
> > + */
> > +int libxl__lock_domain_configuration(libxl__gc *gc, uint32_t domid,
> > +                                     int *fd_lock);
> 
> You need to explain the lifetime semantics of *fd_lock.  Your code
> demands that the caller set it to -1 beforehand (which is fine).
> 

Ack.

> > +int libxl__unlock_domain_configuration(libxl__gc *gc, uint32_t domid,
> > +                                       int *fd_lock);
> 
> If you do retain this as a separate function, it should return void.
> I can think of nothing useful that the caller could do with an error
> from it.
> 

I will retain this as a separate function so that it looks symmetric to
__lock.

Wei.

> Ian.

  reply	other threads:[~2014-07-25 10:36 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 14:32 [PATCH v1 00/10] libxl: synchronise domain configuration Wei Liu
2014-07-10 14:32 ` [PATCH v1 01/10] libxl: libxl-json format and internal functions to get / set it Wei Liu
2014-07-16 16:11   ` Ian Campbell
2014-07-16 16:44     ` Wei Liu
2014-07-24 18:09   ` Ian Jackson
2014-07-24 18:29   ` Ian Jackson
2014-07-25 10:30     ` Wei Liu
2014-07-25 14:51       ` Ian Jackson
2014-07-10 14:32 ` [PATCH v1 02/10] libxl_internal: functions to lock / unlock domain configuration Wei Liu
2014-07-16 16:15   ` Ian Campbell
2014-07-16 16:44     ` Wei Liu
2014-07-17 11:29       ` Ian Campbell
2014-07-17 11:41         ` Wei Liu
2014-07-17 11:48           ` Ian Campbell
2014-07-24 18:24   ` Ian Jackson
2014-07-25 10:36     ` Wei Liu [this message]
2014-07-10 14:32 ` [PATCH v1 03/10] libxl: store a copy of vanilla domain configuration when creating domain Wei Liu
2014-07-16 16:18   ` Ian Campbell
2014-07-16 16:47     ` Wei Liu
2014-07-17 11:06       ` Ian Campbell
2014-07-17 11:46         ` Wei Liu
2014-07-24 18:52   ` Ian Jackson
2014-07-25 10:53     ` Wei Liu
2014-07-25 15:01       ` Ian Jackson
2014-07-25 15:43         ` Wei Liu
2014-07-25 17:14           ` Ian Jackson
2014-07-25 17:34             ` Wei Liu
2014-07-25 18:31               ` Ian Jackson
2014-07-25 19:47                 ` Wei Liu
2014-07-28  9:42                   ` Ian Campbell
2014-07-28  9:50                   ` Ian Jackson
2014-07-10 14:32 ` [PATCH v1 04/10] libxl: separate device add/rm complete callbacks Wei Liu
2014-07-16 16:26   ` Ian Campbell
2014-07-16 16:48     ` Wei Liu
2014-07-10 14:32 ` [PATCH v1 05/10] libxl: synchronise configuration when we hotplug a device Wei Liu
2014-07-16 16:48   ` Ian Campbell
2014-07-16 17:12     ` Wei Liu
2014-07-17 11:44       ` Ian Campbell
2014-07-17 14:13         ` Wei Liu
2014-07-18  8:49           ` Ian Campbell
2014-07-18 11:22             ` Wei Liu
2014-07-18 12:20               ` Ian Campbell
2014-07-18 13:41                 ` Wei Liu
2014-07-18 13:44                   ` Ian Campbell
2014-07-25 16:06   ` Ian Jackson
2014-07-25 16:40     ` Wei Liu
2014-07-25 17:11       ` Ian Jackson
2014-07-25 17:19         ` Wei Liu
2014-07-10 14:32 ` [PATCH v1 06/10] libxl: synchronise configuration when we remove/destroy " Wei Liu
2014-07-16 16:58   ` Ian Campbell
2014-07-10 14:32 ` [PATCH v1 07/10] libxl: make libxl_cd_insert "eject" + "insert" Wei Liu
2014-07-17 10:44   ` Ian Campbell
2014-07-17 14:20     ` Wei Liu
2014-07-10 14:32 ` [PATCH v1 08/10] libxl: introduce libxl_get_memory_static_max Wei Liu
2014-07-17 10:47   ` Ian Campbell
2014-07-17 12:02     ` Wei Liu
2014-07-17 13:59       ` Ian Campbell
2014-07-29 13:39         ` Ian Jackson
2014-07-10 14:32 ` [PATCH v1 09/10] libxl: introduce libxl_retrieve_domain_configuration Wei Liu
2014-07-17 10:59   ` Ian Campbell
2014-07-17 12:11     ` Wei Liu
2014-07-17 14:02       ` Ian Campbell
2014-07-17 14:28         ` Wei Liu
2014-07-18  8:52           ` Ian Campbell
2014-07-18 11:17             ` Wei Liu
2014-07-29 15:31       ` Ian Jackson
2014-07-29 15:29     ` Ian Jackson
2014-07-10 14:32 ` [PATCH v1 10/10] xl: use libxl_retrieve_domain_configuration and JSON format Wei Liu
2014-07-17 11:13   ` Ian Campbell
2014-07-17 12:14     ` Wei Liu

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=20140725103637.GI28444@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.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).