All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] libxc: make unlock_page return error
Date: Thu, 19 Aug 2010 17:39:29 +0200	[thread overview]
Message-ID: <201008191739.30032.Christoph.Egger@amd.com> (raw)
In-Reply-To: <1282229841.3170.3073.camel@zakaz.uk.xensource.com>

On Thursday 19 August 2010 16:57:21 Ian Campbell wrote:
> On Thu, 2010-08-19 at 15:46 +0100, Ian Jackson wrote:
> > Christoph Egger writes ("[Xen-devel] [PATCH] libxc: make unlock_page 
return error"):
> > > As a result of debugging 'xend segfaults when starting',
> > > the attached patch makes unlock_pages return an error.
> >
> > Having read this in more detail, it seems that you're making
> > {lock,unlock}_pages return errno values on error.  That's fine but
> > it's quite unusual in libxc; all libxc functions normally return -1 on
> > error and set errno.
> >
> > So I think the unusual return value convention is worth a comment in
> > xc_private.h.  Can you please resubmit with such a comment ?
>
> I think it should just follow the normal libxc convention instead of
> commenting on the use of an unusual return value convention.
>
> I also think that such a patch must include (or be part of a series
> which) updates the callers to actually do something with the new return
> value, or else it is somewhat pointless.
>
> Given that this patch was only for debugging purposes for an issue which
> is now resolved is there any need?

The need I see for now is a future regression.

Christoph



-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2010-08-19 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 14:42 [PATCH] libxc: make unlock_page return error Christoph Egger
2010-08-18 16:05 ` Ian Jackson
2010-08-19  8:44   ` Christoph Egger
2010-08-19 14:43     ` Ian Jackson
2010-08-19 14:46 ` Ian Jackson
2010-08-19 14:57   ` Ian Campbell
2010-08-19 15:39     ` Christoph Egger [this message]
2010-08-19 16:01       ` Ian Campbell
2010-08-19 16:35         ` Tim Deegan

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=201008191739.30032.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.