Re: [PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2019-04-13 Thread Sasha Levin
On Sat, Apr 13, 2019 at 08:41:33PM +0800, Nicolas Boichat wrote: Dear stable maintainers, I encountered a similar issue on a 4.19.33 kernel (Chromium OS). On my board, the system would not even be able to boot if KASLR decides to map the linear region to the top of the virtual address space. Thi

Re: [PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2019-04-13 Thread Nicolas Boichat
Dear stable maintainers, I encountered a similar issue on a 4.19.33 kernel (Chromium OS). On my board, the system would not even be able to boot if KASLR decides to map the linear region to the top of the virtual address space. This happens every 253 boots on average (there are 0xfd possible rando

Re: [PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2019-01-16 Thread Yueyi Li
On 2019/1/16 15:51, Ard Biesheuvel wrote: > On Wed, 16 Jan 2019 at 04:37, Yueyi Li wrote: >> OK, thanks. But seems this mail be ignored, do i need re-sent the patch? >> >> On 2018/12/26 21:49, Ard Biesheuvel wrote: >>> On Tue, 25 Dec 2018 at 03:30, Yueyi Li wrote: Hi Ard, On

Re: [PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2019-01-15 Thread Ard Biesheuvel
On Wed, 16 Jan 2019 at 04:37, Yueyi Li wrote: > > OK, thanks. But seems this mail be ignored, do i need re-sent the patch? > > On 2018/12/26 21:49, Ard Biesheuvel wrote: > > On Tue, 25 Dec 2018 at 03:30, Yueyi Li wrote: > >> Hi Ard, > >> > >> > >> On 2018/12/24 17:45, Ard Biesheuvel wrote: > >>>

Re: [PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2019-01-15 Thread Yueyi Li
OK, thanks. But seems this mail be ignored, do i need re-sent the patch? On 2018/12/26 21:49, Ard Biesheuvel wrote: > On Tue, 25 Dec 2018 at 03:30, Yueyi Li wrote: >> Hi Ard, >> >> >> On 2018/12/24 17:45, Ard Biesheuvel wrote: >>> Does the following change fix your issue as well? >>> >>> index 9b

Re: [PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2018-12-26 Thread Ard Biesheuvel
On Tue, 25 Dec 2018 at 03:30, Yueyi Li wrote: > > Hi Ard, > > > On 2018/12/24 17:45, Ard Biesheuvel wrote: > > Does the following change fix your issue as well? > > > > index 9b432d9fcada..9dcf0ff75a11 100644 > > --- a/arch/arm64/mm/init.c > > +++ b/arch/arm64/mm/init.c > > @@ -447,7 +447,7 @@ voi

Re: [PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2018-12-24 Thread Yueyi Li
Hi Ard, On 2018/12/24 17:45, Ard Biesheuvel wrote: > Does the following change fix your issue as well? > > index 9b432d9fcada..9dcf0ff75a11 100644 > --- a/arch/arm64/mm/init.c > +++ b/arch/arm64/mm/init.c > @@ -447,7 +447,7 @@ void __init arm64_memblock_init(void) > * memory spa

Re: [PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2018-12-24 Thread Ard Biesheuvel
On Mon, 24 Dec 2018 at 08:40, Yueyi Li wrote: > > When KASLR enaled(CONFIG_RANDOMIZE_BASE=y), the top 4K virtual > address have chance to be mapped to physical address, but which > is expected to leave room for ERR_PTR. > > Also, it might cause some other warparound issue when somewhere > use the

[PATCH] arm64: kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region

2018-12-23 Thread Yueyi Li
When KASLR enaled(CONFIG_RANDOMIZE_BASE=y), the top 4K virtual address have chance to be mapped to physical address, but which is expected to leave room for ERR_PTR. Also, it might cause some other warparound issue when somewhere use the last memory page but no overflow check. Such as the last pag