On Tue, 8 Jul 2014, David Herrmann wrote:
>
> Hugh, any comments on patch 5, 6 and 7? Those are the last outstanding
> issues with memfd+sealing. Patch 7 (isolating pages) is still my
> favorite and has been running just fine on my machine for the last
> months. I think it'd be nice if we could
On Tue, 8 Jul 2014, David Herrmann wrote:
Hugh, any comments on patch 5, 6 and 7? Those are the last outstanding
issues with memfd+sealing. Patch 7 (isolating pages) is still my
favorite and has been running just fine on my machine for the last
months. I think it'd be nice if we could give
Hi
On Fri, Jun 13, 2014 at 12:36 PM, David Herrmann wrote:
> Hi
>
> This is v3 of the File-Sealing and memfd_create() patches. You can find v1
> with
> a longer introduction at gmane:
> http://thread.gmane.org/gmane.comp.video.dri.devel/102241
> An LWN article about memfd+sealing is
Hi
On Fri, Jun 13, 2014 at 12:36 PM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
This is v3 of the File-Sealing and memfd_create() patches. You can find v1
with
a longer introduction at gmane:
http://thread.gmane.org/gmane.comp.video.dri.devel/102241
An LWN article about
On Tue, Jun 17, 2014 at 1:31 PM, Hugh Dickins wrote:
> On Tue, 17 Jun 2014, Andy Lutomirski wrote:
>> On Tue, Jun 17, 2014 at 9:51 AM, David Herrmann
>> wrote:
>> > On Tue, Jun 17, 2014 at 6:41 PM, Andy Lutomirski
>> > wrote:
>> >> On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann
>> >>
On Tue, 17 Jun 2014, Andy Lutomirski wrote:
> On Tue, Jun 17, 2014 at 9:51 AM, David Herrmann wrote:
> > On Tue, Jun 17, 2014 at 6:41 PM, Andy Lutomirski
> > wrote:
> >> On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann
> >> wrote:
> >>> On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski
> >>>
On Tue, Jun 17, 2014 at 9:51 AM, David Herrmann wrote:
> Hi
>
> On Tue, Jun 17, 2014 at 6:41 PM, Andy Lutomirski wrote:
>> On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann
>> wrote:
>>> Hi
>>>
>>> On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski
>>> wrote:
Can you summarize why holes
Hi
On Tue, Jun 17, 2014 at 6:41 PM, Andy Lutomirski wrote:
> On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann wrote:
>> Hi
>>
>> On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski wrote:
>>> Can you summarize why holes can't be reliably backed by the zero page?
>>
>> To answer this, I will quote
On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann wrote:
> Hi
>
> On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski wrote:
>> Can you summarize why holes can't be reliably backed by the zero page?
>
> To answer this, I will quote Hugh from "PATCH v2 1/3":
>
>> We do already use the ZERO_PAGE
Hi
On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski wrote:
> Can you summarize why holes can't be reliably backed by the zero page?
To answer this, I will quote Hugh from "PATCH v2 1/3":
> We do already use the ZERO_PAGE instead of allocating when it's a
> simple read; and on the face of it,
Hi
On Tue, Jun 17, 2014 at 2:13 PM, Florian Weimer wrote:
> On 06/17/2014 12:10 PM, David Herrmann wrote:
>
The file might have holes, therefore, you'd have to allocate backing
pages. This might hit a soft-limit and fail. To avoid this, use
fallocate() to allocate pages prior to
On 06/17/2014 12:10 PM, David Herrmann wrote:
The file might have holes, therefore, you'd have to allocate backing
pages. This might hit a soft-limit and fail. To avoid this, use
fallocate() to allocate pages prior to mmap()
This does not work because the consuming side does not know how the
Hi
On Tue, Jun 17, 2014 at 12:04 PM, Florian Weimer wrote:
> On 06/17/2014 12:01 PM, David Herrmann wrote:
>
>>> I don't think this is what potential users expect because mlock requires
>>> capabilities which are not available to them.
>>>
>>> A couple of weeks ago, sealing was to be applied to
On 06/17/2014 12:01 PM, David Herrmann wrote:
I don't think this is what potential users expect because mlock requires
capabilities which are not available to them.
A couple of weeks ago, sealing was to be applied to anonymous shared memory.
Has this changed? Why should *reading* it trigger
Hi
On Tue, Jun 17, 2014 at 11:54 AM, Florian Weimer wrote:
> On 06/13/2014 05:33 PM, David Herrmann wrote:
>>
>> On Fri, Jun 13, 2014 at 5:17 PM, Andy Lutomirski
>> wrote:
>>>
>>> Isn't the point of SEAL_SHRINK to allow servers to mmap and read
>>> safely without worrying about SIGBUS?
>>
>>
>>
On 06/13/2014 05:33 PM, David Herrmann wrote:
On Fri, Jun 13, 2014 at 5:17 PM, Andy Lutomirski wrote:
Isn't the point of SEAL_SHRINK to allow servers to mmap and read
safely without worrying about SIGBUS?
No, I don't think so.
The point of SEAL_SHRINK is to prevent a file from shrinking.
On 06/13/2014 05:33 PM, David Herrmann wrote:
On Fri, Jun 13, 2014 at 5:17 PM, Andy Lutomirski l...@amacapital.net wrote:
Isn't the point of SEAL_SHRINK to allow servers to mmap and read
safely without worrying about SIGBUS?
No, I don't think so.
The point of SEAL_SHRINK is to prevent a file
Hi
On Tue, Jun 17, 2014 at 11:54 AM, Florian Weimer fwei...@redhat.com wrote:
On 06/13/2014 05:33 PM, David Herrmann wrote:
On Fri, Jun 13, 2014 at 5:17 PM, Andy Lutomirski l...@amacapital.net
wrote:
Isn't the point of SEAL_SHRINK to allow servers to mmap and read
safely without worrying
On 06/17/2014 12:01 PM, David Herrmann wrote:
I don't think this is what potential users expect because mlock requires
capabilities which are not available to them.
A couple of weeks ago, sealing was to be applied to anonymous shared memory.
Has this changed? Why should *reading* it trigger
Hi
On Tue, Jun 17, 2014 at 12:04 PM, Florian Weimer fwei...@redhat.com wrote:
On 06/17/2014 12:01 PM, David Herrmann wrote:
I don't think this is what potential users expect because mlock requires
capabilities which are not available to them.
A couple of weeks ago, sealing was to be applied
On 06/17/2014 12:10 PM, David Herrmann wrote:
The file might have holes, therefore, you'd have to allocate backing
pages. This might hit a soft-limit and fail. To avoid this, use
fallocate() to allocate pages prior to mmap()
This does not work because the consuming side does not know how the
Hi
On Tue, Jun 17, 2014 at 2:13 PM, Florian Weimer fwei...@redhat.com wrote:
On 06/17/2014 12:10 PM, David Herrmann wrote:
The file might have holes, therefore, you'd have to allocate backing
pages. This might hit a soft-limit and fail. To avoid this, use
fallocate() to allocate pages prior
Hi
On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski l...@amacapital.net wrote:
Can you summarize why holes can't be reliably backed by the zero page?
To answer this, I will quote Hugh from PATCH v2 1/3:
We do already use the ZERO_PAGE instead of allocating when it's a
simple read; and on the
On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski l...@amacapital.net wrote:
Can you summarize why holes can't be reliably backed by the zero page?
To answer this, I will quote Hugh from PATCH v2 1/3:
We do
Hi
On Tue, Jun 17, 2014 at 6:41 PM, Andy Lutomirski l...@amacapital.net wrote:
On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski l...@amacapital.net wrote:
Can you summarize why holes can't be reliably backed by
On Tue, Jun 17, 2014 at 9:51 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Tue, Jun 17, 2014 at 6:41 PM, Andy Lutomirski l...@amacapital.net wrote:
On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann dh.herrm...@gmail.com
wrote:
Hi
On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski
On Tue, 17 Jun 2014, Andy Lutomirski wrote:
On Tue, Jun 17, 2014 at 9:51 AM, David Herrmann dh.herrm...@gmail.com wrote:
On Tue, Jun 17, 2014 at 6:41 PM, Andy Lutomirski l...@amacapital.net
wrote:
On Tue, Jun 17, 2014 at 9:36 AM, David Herrmann dh.herrm...@gmail.com
wrote:
On Tue, Jun
On Tue, Jun 17, 2014 at 1:31 PM, Hugh Dickins hu...@google.com wrote:
On Tue, 17 Jun 2014, Andy Lutomirski wrote:
On Tue, Jun 17, 2014 at 9:51 AM, David Herrmann dh.herrm...@gmail.com
wrote:
On Tue, Jun 17, 2014 at 6:41 PM, Andy Lutomirski l...@amacapital.net
wrote:
On Tue, Jun 17, 2014
Hi
On Fri, Jun 13, 2014 at 5:17 PM, Andy Lutomirski wrote:
> On Fri, Jun 13, 2014 at 8:15 AM, David Herrmann wrote:
>> Hi
>>
>> On Fri, Jun 13, 2014 at 5:10 PM, Andy Lutomirski wrote:
>>> On Fri, Jun 13, 2014 at 3:36 AM, David Herrmann
>>> wrote:
Hi
This is v3 of the
On Fri, Jun 13, 2014 at 8:15 AM, David Herrmann wrote:
> Hi
>
> On Fri, Jun 13, 2014 at 5:10 PM, Andy Lutomirski wrote:
>> On Fri, Jun 13, 2014 at 3:36 AM, David Herrmann
>> wrote:
>>> Hi
>>>
>>> This is v3 of the File-Sealing and memfd_create() patches. You can find v1
>>> with
>>> a longer
Hi
On Fri, Jun 13, 2014 at 5:10 PM, Andy Lutomirski wrote:
> On Fri, Jun 13, 2014 at 3:36 AM, David Herrmann wrote:
>> Hi
>>
>> This is v3 of the File-Sealing and memfd_create() patches. You can find v1
>> with
>> a longer introduction at gmane:
>>
On Fri, Jun 13, 2014 at 3:36 AM, David Herrmann wrote:
> Hi
>
> This is v3 of the File-Sealing and memfd_create() patches. You can find v1
> with
> a longer introduction at gmane:
> http://thread.gmane.org/gmane.comp.video.dri.devel/102241
> An LWN article about memfd+sealing is available,
Hi
This is v3 of the File-Sealing and memfd_create() patches. You can find v1 with
a longer introduction at gmane:
http://thread.gmane.org/gmane.comp.video.dri.devel/102241
An LWN article about memfd+sealing is available, too:
https://lwn.net/Articles/593918/
v2 with some more discussions can
Hi
This is v3 of the File-Sealing and memfd_create() patches. You can find v1 with
a longer introduction at gmane:
http://thread.gmane.org/gmane.comp.video.dri.devel/102241
An LWN article about memfd+sealing is available, too:
https://lwn.net/Articles/593918/
v2 with some more discussions can
On Fri, Jun 13, 2014 at 3:36 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
This is v3 of the File-Sealing and memfd_create() patches. You can find v1
with
a longer introduction at gmane:
http://thread.gmane.org/gmane.comp.video.dri.devel/102241
An LWN article about memfd+sealing is
Hi
On Fri, Jun 13, 2014 at 5:10 PM, Andy Lutomirski l...@amacapital.net wrote:
On Fri, Jun 13, 2014 at 3:36 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
This is v3 of the File-Sealing and memfd_create() patches. You can find v1
with
a longer introduction at gmane:
On Fri, Jun 13, 2014 at 8:15 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Fri, Jun 13, 2014 at 5:10 PM, Andy Lutomirski l...@amacapital.net wrote:
On Fri, Jun 13, 2014 at 3:36 AM, David Herrmann dh.herrm...@gmail.com
wrote:
Hi
This is v3 of the File-Sealing and memfd_create()
Hi
On Fri, Jun 13, 2014 at 5:17 PM, Andy Lutomirski l...@amacapital.net wrote:
On Fri, Jun 13, 2014 at 8:15 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Fri, Jun 13, 2014 at 5:10 PM, Andy Lutomirski l...@amacapital.net wrote:
On Fri, Jun 13, 2014 at 3:36 AM, David Herrmann
38 matches
Mail list logo
