On Mon, Mar 11, 2019 at 12:56:14PM +, Daniel P. Berrangé wrote:
> On Mon, Mar 11, 2019 at 01:50:37PM +0100, Marc-André Lureau wrote:
> > Hi
> >
> > On Mon, Mar 11, 2019 at 1:35 PM Ilya Maximets
> > wrote:
> > >
> > > Hi.
> > >
> > > I'm trying to figure out the state of this patch set.
> > >
On Mon, Mar 11, 2019 at 11:12:29AM -0300, Eduardo Habkost wrote:
> On Mon, Mar 11, 2019 at 12:56:14PM +, Daniel P. Berrangé wrote:
> > On Mon, Mar 11, 2019 at 01:50:37PM +0100, Marc-André Lureau wrote:
> > > Hi
> > >
> > > On Mon, Mar 11, 2019 at 1:35 PM Ilya Maximets
> > > wrote:
> > > >
>
On Mon, Mar 11, 2019 at 01:50:37PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Mon, Mar 11, 2019 at 1:35 PM Ilya Maximets wrote:
> >
> > Hi.
> >
> > I'm trying to figure out the state of this patch set.
> > Is there any chance for it to be accepted?
> >
> > The first patch needs minor rebase. I c
Hi
On Mon, Mar 11, 2019 at 1:35 PM Ilya Maximets wrote:
>
> Hi.
>
> I'm trying to figure out the state of this patch set.
> Is there any chance for it to be accepted?
>
> The first patch needs minor rebase. I could send a new version.
Please do,
I prefer the solution proposed in v2: do not regi
Hi.
I'm trying to figure out the state of this patch set.
Is there any chance for it to be accepted?
The first patch needs minor rebase. I could send a new version.
BTW, even without the first patch that raised some discussion
the last three patches are kind of straightforward and useful.
Best
Version 2:
* First patch changed to just drop the memfd backend
if seals are not supported.
Ilya Maximets (4):
hostmem-memfd: disable for systems wihtout sealing support
memfd: always check for MFD_CLOEXEC
memfd: set up correct errno if not supported
memfd: improve error messages
