linux-kernel - Re: m68k Kconfig warning

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <CACz-3rjOPg_rMt_FbJ5_nKLpjTK-Bv=amGsJpXwqbTBNX4YA7w@mail.gmail.com>
Date:   Mon, 2 Dec 2019 12:42:07 +0100
From:   Kars de Jong <karsdejong@...e.nl>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        linux-m68k <linux-m68k@...ts.linux-m68k.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: m68k Kconfig warning

Hi Geert & Randy,

Op wo 27 nov. 2019 om 08:12 schreef Geert Uytterhoeven <geert@...ux-m68k.org>:
> On Wed, Nov 27, 2019 at 2:27 AM Randy Dunlap <rdunlap@...radead.org> wrote:
> > Just noticed this.  I don't know what the right fix is.
> > Would you take care of it, please?
> >
> > on Linux 5.4, m68k allmodconfig:
> >
> > WARNING: unmet direct dependencies detected for NEED_MULTIPLE_NODES
> >   Depends on [n]: DISCONTIGMEM [=n] || NUMA
> >   Selected by [y]:
> >   - SINGLE_MEMORY_CHUNK [=y] && MMU [=y]
>
> This has been basically there forever, but working.

The reason for SINGLE_MEMORY_CHUNK depending on NEED_MULTIPLE_NODES is
historic due to the way it is implemented.
I played with it this weekend and I got a working version of FLATMEM,
which can replace SINGLE_MEMORY_CHUNK.

I'll clean it up and send a patch later this week. A possible next
step might be to replace DISCONTIGMEM with SPARSEMEM (since
DISCONTIGMEM has been deprecated).

Kind regards,

Kars.