Re: [Xen-devel] [PATCH] tools/libxenforeignmemory: add a call to restrict the handle

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@xxxxxxxxxxxxx] On Behalf Of
> Paul Durrant
> Sent: 24 March 2017 20:24
> To: Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>; xen-
> devel@xxxxxxxxxxxxxxxxxxxx
> Cc: Ian Jackson <Ian.Jackson@xxxxxxxxxx>; Julien Grall
> <julien.grall@xxxxxxx>; Wei Liu <wei.liu2@xxxxxxxxxx>
> Subject: Re: [Xen-devel] [PATCH] tools/libxenforeignmemory: add a call to
> restrict the handle
> 
> > -----Original Message-----
> > From: Andrew Cooper
> > Sent: 24 March 2017 20:10
> > To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>; xen-
> devel@xxxxxxxxxxxxxxxxxxxx
> > Cc: Wei Liu <wei.liu2@xxxxxxxxxx>; Ian Jackson <Ian.Jackson@xxxxxxxxxx>;
> > Julien Grall <julien.grall@xxxxxxx>
> > Subject: Re: [Xen-devel] [PATCH] tools/libxenforeignmemory: add a call to
> > restrict the handle
> >
> > On 22/03/17 11:25, Paul Durrant wrote:
> > > diff --git a/tools/libs/foreignmemory/libxenforeignmemory.map
> > b/tools/libs/foreignmemory/libxenforeignmemory.map
> > > index df206b3..5c9806c 100644
> > > --- a/tools/libs/foreignmemory/libxenforeignmemory.map
> > > +++ b/tools/libs/foreignmemory/libxenforeignmemory.map
> > > @@ -4,5 +4,6 @@ VERS_1.0 {
> > >           xenforeignmemory_close;
> > >           xenforeignmemory_map;
> > >           xenforeignmemory_unmap;
> > > +         xenforeignmemory_restrict;
> > >   local: *; /* Do not expose anything by default */
> > >  };
> >
> > This isn't correct.
> >
> > New functions like this need to bump at least the SO minor version, like
> > c/s f1446de4ba
> >
> 
> Sorry, yes, I forgot these libraries are supposed to be stable now.
> 
> > Fixing this is a blocker to releasing 4.9
> >
> 
> I'll submit a patch on Monday.

Actually, on second thoughts, do we want to bump the version for all changes or 
just incompatible ones? I added a call here so it shouldn't break any older 
application compiling against this library.

  Paul

> 
> > Also, we should really get automatic ABI checking built into the release
> > process, to prevent mistakes like this from happening accidentally.
> >
> 
> Yes, definitely.
> 
>   Paul
> 
> > ~Andrew
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel