On 09/02/16 05:56 AM, Pekka Paalanen wrote:
> On Mon, 08 Feb 2016 12:23:58 -0600
> Derek Foreman wrote:
>
>> On 05/02/16 08:50 AM, Derek Foreman wrote:
>>> On 05/02/16 07:25 AM, Pekka Paalanen wrote:
From: Pekka Paalanen
Since shm_pool_resize() uses mremap(MREMAP_MAYMOVE), the p
On Mon, 08 Feb 2016 12:23:58 -0600
Derek Foreman wrote:
> On 05/02/16 08:50 AM, Derek Foreman wrote:
> > On 05/02/16 07:25 AM, Pekka Paalanen wrote:
> >> From: Pekka Paalanen
> >>
> >> Since shm_pool_resize() uses mremap(MREMAP_MAYMOVE), the pool's base
> >> address may change at that point.
>
On 05/02/16 08:50 AM, Derek Foreman wrote:
> On 05/02/16 07:25 AM, Pekka Paalanen wrote:
>> From: Pekka Paalanen
>>
>> Since shm_pool_resize() uses mremap(MREMAP_MAYMOVE), the pool's base
>> address may change at that point.
>>
>> If a compositor stores the pointer and a client enlarges the pool,
On 05/02/16 07:25 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> Since shm_pool_resize() uses mremap(MREMAP_MAYMOVE), the pool's base
> address may change at that point.
>
> If a compositor stores the pointer and a client enlarges the pool, the
> compositor will have a stale pointer.
>
>
From: Pekka Paalanen
Since shm_pool_resize() uses mremap(MREMAP_MAYMOVE), the pool's base
address may change at that point.
If a compositor stores the pointer and a client enlarges the pool, the
compositor will have a stale pointer.
Signed-off-by: Pekka Paalanen
---
src/wayland-shm.c | 4