linux-kernel - More problems in setup_pcpu

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

Message-Id: <20090401.213112.96144152.davem@davemloft.net>
Date:	Wed, 01 Apr 2009 21:31:12 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	tj@...nel.org
CC:	linux-kernel@...r.kernel.org
Subject: More problems in setup_pcpu_remap()

The way this code is currently designed, it can exhaust all of the
VMALLOC address space on both x86 and x86_64, and then some.

It allocates PMD_SIZE * num_possible_cpus() of vmalloc space.

PMD_SIZE is 2MB, num_possible_cpus() can be up to 4096....
which can easily exceed (VMALLOC_END - VMALLOC_START)

Initially I had set out to implement sparc64 support for the new
per-cpu stuff, but it looks like I'm stuck finding bugs in the x86
implementation instead :-)
--
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/