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 gi
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 available,
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
>> >> 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
> >> wrote:
> >>> On Tue, Jun 17, 2014 at 6:20 PM, Andy Lutomirski
> >>> w
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 can'
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 H
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 instead
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, we
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 mm
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
d
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 a
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 OO
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. SIGB
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 File-Seali
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 i
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:
>> http://thread.gmane.org/gmane.comp.video.dri
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, too:
18 matches
Mail list logo
