linux-kernel - Re: [PATCH v3 00/13] introduce the Xen PV Calls frontend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.10.1708101112190.12869@sstabellini-ThinkPad-X260>
Date:   Thu, 10 Aug 2017 11:15:03 -0700 (PDT)
From:   Stefano Stabellini <sstabellini@...nel.org>
To:     Boris Ostrovsky <boris.ostrovsky@...cle.com>
cc:     Stefano Stabellini <sstabellini@...nel.org>,
        xen-devel@...ts.xen.org, linux-kernel@...r.kernel.org,
        jgross@...e.com
Subject: Re: [PATCH v3 00/13] introduce the Xen PV Calls frontend

On Thu, 10 Aug 2017, Boris Ostrovsky wrote:
> On 07/31/2017 06:57 PM, Stefano Stabellini wrote:
> > Hi all,
> >
> > this series introduces the frontend for the newly introduced PV Calls
> > procotol.
> >
> > PV Calls is a paravirtualized protocol that allows the implementation of
> > a set of POSIX functions in a different domain. The PV Calls frontend
> > sends POSIX function calls to the backend, which implements them and
> > returns a value to the frontend and acts on the function call.
> >
> > For more information about PV Calls, please read:
> >
> > https://xenbits.xen.org/docs/unstable/misc/pvcalls.html
> >
> > This patch series only implements the frontend driver. It doesn't
> > attempt to redirect POSIX calls to it. The functions exported in
> > pvcalls-front.h are meant to be used for that. A separate patch series
> > will be sent to use them and hook them into the system.
> 
> Stefano,
> 
> 
> Should this be reviewed or are you going to send another version?

Sorry for the delay, I am dealing with a personal issue at the moment
and I didn't manage to address your valid comments on the release
function implementation.

However in this version I did address all other comments, so it would be
good if you could give a look at it, bearing in mind that the problem on
release is still unaddressed here.

Thanks,

Stefano