lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 3 May 2020 22:20:39 +0200
From:   Arnd Bergmann <>
To:     afzal mohammed <>
Cc:     Russell King <>,
        Alan Kao <>,
        Eric Lin <>, Gary Guo <>,, David Abdurachmanov <>,
        Anup Patel <>,
        "" <>,
        Andrew Morton <>,
        Steven Price <>,,, Albert Ou <>,
        Palmer Dabbelt <>,
        Greentime Hu <>,,
        Paul Walmsley <>,
        Mike Rapoport <>,
        Thomas Gleixner <>,
        Borislav Petkov <>,
        Logan Gunthorpe <>,
Subject: Re: [PATCH 0/3] Highmem support for 32-bit RISC-V

On Sun, May 3, 2020 at 4:50 PM afzal mohammed <> wrote:
> Hi Arnd,
> > On Tue, Apr 14, 2020 at 09:29:46PM +0200, Arnd Bergmann wrote:
> > > Another thing to try early is to move the vmlinux virtual address
> > > from the linear mapping into vmalloc space. This does not require
> > > LPAE either, but it only works on relatively modern platforms that
> > > don't have conflicting fixed mappings there.
> i have started by attempting to move static kernel mapping from lowmem
> to vmalloc space. At boot the execution so far has went past assembly
> & reached C, to be specific, arm_memblock_init [in setup_arch()],
> currently debugging the hang that happens after that point.

Ah, good start. Which SoC platform are you running this on? Just making
sure that this won't conflict with static mappings later.

One problem I see immediately in arm_memblock_init() is that it uses
__pa() to convert from virtual address in the linear map to physical,
but now you actually pass an address that is in vmalloc rather than
the linear map. There are certainly more problems like this to come.

> To make things easier in the beginning, ARM_PATCH_PHYS_VIRT is disabled &
> platform specific PHYS_OFFSET is fed, this is planned to be fixed once
> it boots.
> [ i will probably start a new thread or hopefully RFC on LAKML ]

Ok, makes sense.


Powered by blists - more mailing lists