netdev - Re: panic in udp_init() when using FORCE_NR

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] [day] [month] [year] [list]

Message-ID: <20230613184146.66d89282@espresso.lan.box>
Date: Tue, 13 Jun 2023 18:41:46 -0300
From: Ricardo Nabinger Sanchez <rnsanchez@...il.com>
To: Eric Dumazet <edumazet@...gle.com>
Cc: "David S. Miller" <davem@...emloft.net>, Willem de Bruijn
 <willemdebruijn.kernel@...il.com>, netdev@...r.kernel.org
Subject: Re: panic in udp_init() when using FORCE_NR_CPUS

On Tue, 13 Jun 2023 23:05:34 +0200
Eric Dumazet <edumazet@...gle.com> wrote:

> I suspect you run with LOCKDEP enabled (CONFIG_PROVE_LOCKING=y)
> and a very big NR_CPUS ?
> 
> LOCKDEP makes spinlock_t 16 times bigger :/
> 
> If so, please try the following fix.

CONFIG_LOCKDEP_SUPPORT=y

Now I'm using only 12 CPUs, per my other message where I disabled MAXSMP
and really set NR_CPUS, resulting in a successful boot.

It may be true that earlier it was architectures's max (8192).  Maybe
that was the real issue, then?

Best regards,

-- 
Ricardo Nabinger Sanchez

    Dedique-se a melhorar seus esforços.
    Todas as suas conquistas evolutivas não foram resultado dos
    deuses, das outras consciências, ou do acaso, mas unicamente
    da sua transpiração. ---Waldo Vieira, Léxico de Ortopensatas