linux-kernel - [PATCH 0/6] Final cpumask conversion patches for 4096+ cpus

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

Message-Id: <200911191928.38048.rusty@rustcorp.com.au>
Date:	Thu, 19 Nov 2009 19:28:37 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>, Mike Travis <travis@....com>
Subject: [PATCH 0/6] Final cpumask conversion patches for 4096+ cpus

Finally, these 6 patches actually allocate short (nr_cpu_ids-bits) cpumasks
and nail down the lid so the compiler will find new abuses if they creep in.

For non-CONFIG_CPUMASK_OFFSTACK:
   The only visible changes are that you have to use the accessors
   mm_cpumask() and tsk_cpumask.  They convert the bitmaps (moved to the end
   of those structs) to 'struct cpumask *'.

For CONFIG_CPUMASK_OFFSTACK=y:
   We allocate the mm and task_struct bitmaps short (nr_cpu_ids, rather
   than the compile-time NR_CPUS).  A couple of patches get rid of the
   old-style cpus_ ops so noone uses them accidentally.  We don't define
   struct cpumask at all, which prevents accidental abuse.  Finally, we
   reduce cpumask_size() so our dynamically-allocated cpumasks are only
   nr_cpu_ids big.

Cheers,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/