pipewire: mem: pw_memblock_map(): fix pointer when reusing mapping
Previously the pointer was determined as follows:
mm->this.ptr = SPA_PTROFF(m->ptr, range.start, void);
however, when `pw_map_range` is calculated, `pw_map_range::start` is the offset
from the beginning of the first page, starting at `pw_map_range::offset`.
This works correctly if `memblock_map()` runs because that will map the file
with expected offset, so using `range.start` is correct.
However, when a mapping is reused (i.e. `memblock_find_mapping()`) finds something,
then `range.start` is not necessarily correct. Consider the following example:
* page size is 10
* one memblock with size 20 (2 pages)
* the applications wants to mappings:
* (offset=5,size=10)
* (offset=15,size=5)
After the first request from the application, a `mapping` object is created
that covers the first two pages of the memblock: offset=0 and size=20. During
the second request, the calculated `pw_map_range` is as follows:
{ start = 5, offset = 10, size = 10 }
and the only previously created mapping is reused since (0 <= 5) and (10 <= 20). When
the pointer of the mapping is adjusted afterwards it will be incorrect since `m->ptr`
points to byte 0 on page 0 (instead of byte 0 on page 1 -- that is assumed). Thereforce
the two will unexpectedly overlap.
Fix that by using `offset - m->offset` when adjusting the mapping's pointer. Also move
the `range` variable into a smaller scope because it only makes sense there. And add
a test that check the above previously incorrect case.
Fixes: 2caf81c97c0aee ("mem: improve memory handling")
Fixes #4884
2025-09-08 12:47:10 +02:00
|
|
|
/* PipeWire */
|
|
|
|
|
/* SPDX-FileCopyrightText: Copyright © 2025 PipeWire authors */
|
|
|
|
|
/* SPDX-License-Identifier: MIT */
|
|
|
|
|
|
|
|
|
|
#include <unistd.h>
|
|
|
|
|
|
|
|
|
|
#include <pipewire/mem.h>
|
|
|
|
|
#include <spa/buffer/buffer.h>
|
|
|
|
|
|
|
|
|
|
#include "pwtest.h"
|
|
|
|
|
|
|
|
|
|
PWTEST(mempool_issue4884)
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* See https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4884. This
|
|
|
|
|
* test checks if the offset is correctly applied when a mapping is reused.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
long page_size = sysconf(_SC_PAGESIZE);
|
|
|
|
|
pwtest_errno_ok(page_size);
|
|
|
|
|
pwtest_int_ge(page_size, 8);
|
|
|
|
|
|
|
|
|
|
struct pw_mempool *p = pw_mempool_new(NULL);
|
|
|
|
|
pwtest_ptr_notnull(p);
|
|
|
|
|
|
|
|
|
|
struct pw_memblock *b = pw_mempool_alloc(p, PW_MEMBLOCK_FLAG_READWRITE, SPA_DATA_MemFd, 2 * page_size);
|
|
|
|
|
pwtest_ptr_notnull(b);
|
|
|
|
|
|
|
|
|
|
struct pw_memmap *m1 = pw_mempool_map_id(p, b->id, PW_MEMMAP_FLAG_READWRITE, page_size / 2, page_size, NULL);
|
|
|
|
|
pwtest_ptr_notnull(m1);
|
|
|
|
|
pwtest_ptr_eq(m1->block, b);
|
|
|
|
|
|
|
|
|
|
struct pw_memmap *m2 = pw_mempool_map_id(p, b->id, PW_MEMMAP_FLAG_READWRITE, 3 * page_size / 2, page_size / 2, NULL);
|
|
|
|
|
pwtest_ptr_notnull(m2);
|
|
|
|
|
pwtest_ptr_eq(m2->block, b);
|
|
|
|
|
|
|
|
|
|
pwtest_int_eq(SPA_PTRDIFF(m2->ptr, m1->ptr), page_size);
|
|
|
|
|
|
|
|
|
|
pw_mempool_destroy(p);
|
|
|
|
|
|
|
|
|
|
return PWTEST_PASS;
|
|
|
|
|
}
|
|
|
|
|
|
2026-04-08 09:45:28 +02:00
|
|
|
PWTEST(map_range_overflow)
|
pipewire: mem: pw_memblock_map(): fix pointer when reusing mapping
Previously the pointer was determined as follows:
mm->this.ptr = SPA_PTROFF(m->ptr, range.start, void);
however, when `pw_map_range` is calculated, `pw_map_range::start` is the offset
from the beginning of the first page, starting at `pw_map_range::offset`.
This works correctly if `memblock_map()` runs because that will map the file
with expected offset, so using `range.start` is correct.
However, when a mapping is reused (i.e. `memblock_find_mapping()`) finds something,
then `range.start` is not necessarily correct. Consider the following example:
* page size is 10
* one memblock with size 20 (2 pages)
* the applications wants to mappings:
* (offset=5,size=10)
* (offset=15,size=5)
After the first request from the application, a `mapping` object is created
that covers the first two pages of the memblock: offset=0 and size=20. During
the second request, the calculated `pw_map_range` is as follows:
{ start = 5, offset = 10, size = 10 }
and the only previously created mapping is reused since (0 <= 5) and (10 <= 20). When
the pointer of the mapping is adjusted afterwards it will be incorrect since `m->ptr`
points to byte 0 on page 0 (instead of byte 0 on page 1 -- that is assumed). Thereforce
the two will unexpectedly overlap.
Fix that by using `offset - m->offset` when adjusting the mapping's pointer. Also move
the `range` variable into a smaller scope because it only makes sense there. And add
a test that check the above previously incorrect case.
Fixes: 2caf81c97c0aee ("mem: improve memory handling")
Fixes #4884
2025-09-08 12:47:10 +02:00
|
|
|
{
|
2026-04-08 09:45:28 +02:00
|
|
|
/*
|
|
|
|
|
* Test that pw_map_range_init rejects offset + size combinations
|
|
|
|
|
* that would overflow uint32_t, which could cause mmap with a
|
|
|
|
|
* truncated size and subsequent out-of-bounds access.
|
|
|
|
|
*/
|
|
|
|
|
struct pw_map_range range;
|
|
|
|
|
uint32_t page_size = 4096;
|
|
|
|
|
int res;
|
|
|
|
|
|
|
|
|
|
/* Normal case: should succeed */
|
|
|
|
|
res = pw_map_range_init(&range, 0, 4096, page_size);
|
|
|
|
|
pwtest_int_eq(res, 0);
|
|
|
|
|
pwtest_int_eq(range.offset, 0u);
|
|
|
|
|
pwtest_int_eq(range.start, 0u);
|
|
|
|
|
pwtest_int_eq(range.size, 4096u);
|
|
|
|
|
|
|
|
|
|
/* Page-aligned offset: should succeed */
|
|
|
|
|
res = pw_map_range_init(&range, 4096, 4096, page_size);
|
|
|
|
|
pwtest_int_eq(res, 0);
|
|
|
|
|
pwtest_int_eq(range.offset, 4096u);
|
|
|
|
|
pwtest_int_eq(range.start, 0u);
|
|
|
|
|
pwtest_int_eq(range.size, 4096u);
|
|
|
|
|
|
|
|
|
|
/* Non-aligned offset: start gets the remainder */
|
|
|
|
|
res = pw_map_range_init(&range, 100, 4096, page_size);
|
|
|
|
|
pwtest_int_eq(res, 0);
|
|
|
|
|
pwtest_int_eq(range.offset, 0u);
|
|
|
|
|
pwtest_int_eq(range.start, 100u);
|
|
|
|
|
|
|
|
|
|
/* size=0: should succeed */
|
|
|
|
|
res = pw_map_range_init(&range, 0, 0, page_size);
|
|
|
|
|
pwtest_int_eq(res, 0);
|
|
|
|
|
|
|
|
|
|
/* Overflow: non-aligned offset causes start > 0, then start + size wraps */
|
|
|
|
|
res = pw_map_range_init(&range, 4095, 0xFFFFF002, page_size);
|
|
|
|
|
pwtest_int_lt(res, 0);
|
|
|
|
|
|
|
|
|
|
/* Overflow: max size with any non-zero start */
|
|
|
|
|
res = pw_map_range_init(&range, 1, UINT32_MAX, page_size);
|
|
|
|
|
pwtest_int_lt(res, 0);
|
|
|
|
|
|
|
|
|
|
/* Both large but page-aligned: start=0, start+size=0x80000000,
|
|
|
|
|
* round-up doesn't overflow, so this should succeed */
|
|
|
|
|
res = pw_map_range_init(&range, 0x80000000, 0x80000000, page_size);
|
|
|
|
|
pwtest_int_eq(res, 0);
|
|
|
|
|
|
|
|
|
|
/* Non-aligned offset but still fits: start=1, start+size=0x80000001 */
|
|
|
|
|
res = pw_map_range_init(&range, 0x80000001, 0x80000000, page_size);
|
|
|
|
|
pwtest_int_eq(res, 0);
|
|
|
|
|
|
|
|
|
|
/* Overflow: round-up of start+size would exceed uint32 */
|
|
|
|
|
res = pw_map_range_init(&range, 1, UINT32_MAX - 1, page_size);
|
|
|
|
|
pwtest_int_lt(res, 0);
|
|
|
|
|
|
|
|
|
|
/* start=0, size=UINT32_MAX: start + size doesn't wrap, but
|
|
|
|
|
* SPA_ROUND_UP_N to page_size would overflow, so must fail */
|
|
|
|
|
res = pw_map_range_init(&range, 0, UINT32_MAX, page_size);
|
|
|
|
|
pwtest_int_lt(res, 0);
|
|
|
|
|
|
|
|
|
|
return PWTEST_PASS;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PWTEST_SUITE(pw_mempool)
|
|
|
|
|
{
|
|
|
|
|
pwtest_add(mempool_issue4884, PWTEST_NOARG);
|
|
|
|
|
pwtest_add(map_range_overflow, PWTEST_NOARG);
|
pipewire: mem: pw_memblock_map(): fix pointer when reusing mapping
Previously the pointer was determined as follows:
mm->this.ptr = SPA_PTROFF(m->ptr, range.start, void);
however, when `pw_map_range` is calculated, `pw_map_range::start` is the offset
from the beginning of the first page, starting at `pw_map_range::offset`.
This works correctly if `memblock_map()` runs because that will map the file
with expected offset, so using `range.start` is correct.
However, when a mapping is reused (i.e. `memblock_find_mapping()`) finds something,
then `range.start` is not necessarily correct. Consider the following example:
* page size is 10
* one memblock with size 20 (2 pages)
* the applications wants to mappings:
* (offset=5,size=10)
* (offset=15,size=5)
After the first request from the application, a `mapping` object is created
that covers the first two pages of the memblock: offset=0 and size=20. During
the second request, the calculated `pw_map_range` is as follows:
{ start = 5, offset = 10, size = 10 }
and the only previously created mapping is reused since (0 <= 5) and (10 <= 20). When
the pointer of the mapping is adjusted afterwards it will be incorrect since `m->ptr`
points to byte 0 on page 0 (instead of byte 0 on page 1 -- that is assumed). Thereforce
the two will unexpectedly overlap.
Fix that by using `offset - m->offset` when adjusting the mapping's pointer. Also move
the `range` variable into a smaller scope because it only makes sense there. And add
a test that check the above previously incorrect case.
Fixes: 2caf81c97c0aee ("mem: improve memory handling")
Fixes #4884
2025-09-08 12:47:10 +02:00
|
|
|
|
|
|
|
|
return PWTEST_PASS;
|
|
|
|
|
}
|