diff options
| author | Petr Tesarik <ptesarik@suse.com> | 2026-04-10 14:35:06 +0300 |
|---|---|---|
| committer | Marek Szyprowski <m.szyprowski@samsung.com> | 2026-04-30 09:21:34 +0300 |
| commit | 22d0213e55fbb723c2c00dd5aa855a6eaad95b23 (patch) | |
| tree | e6a1d1cf3c5488b926addeb7f9c8c4f1fca2e799 /include/linux/stackprotector.h | |
| parent | 254f49634ee16a731174d2ae34bc50bd5f45e731 (diff) | |
| download | linux-22d0213e55fbb723c2c00dd5aa855a6eaad95b23.tar.xz | |
dma-direct: fix use of max_pfn
Calculate the correct physical address of the last byte of memory. Since
max_pfn is in fact "the PFN of the first page after the highest system RAM
in physical address space", the highest address that might be used for a
DMA buffer is one byte below max_pfn << PAGE_SHIFT.
This fix is unlikely to make any difference in practice. It's just that the
current formula is slightly confusing.
Signed-off-by: Petr Tesarik <ptesarik@suse.com>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Link: https://lore.kernel.org/r/20260410113506.262579-1-ptesarik@suse.com
Diffstat (limited to 'include/linux/stackprotector.h')
0 files changed, 0 insertions, 0 deletions