linux-kernel - [PATCH 0/3] CMPXCHG config options changes

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]

Date:	Thu, 10 Nov 2011 15:04:17 +0100
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Pekka Enberg <penberg@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Jeff Dike <jdike@...toit.com>, Ingo Molnar <mingo@...e.hu>,
	Christoph Lameter <cl@...ux.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org,
	Heiko Carstens <heiko.carstens@...ibm.com>
Subject: [PATCH 0/3] CMPXCHG config options changes

While implementing cmpxchg_double() on s390 I realized that we don't
set CONFIG_CMPXCHG_LOCAL besides the fact that we have support for it.
However setting that option will increase the size of struct page by
eight bytes on 64 bit, which we certainly do not want.
Also, it doesn't make sense that a present cpu feature should increase
the size of struct page.
Besides that it looks like the dependency to CMPXCHG_LOCAL is wrong
and that it should depend on CMPXCHG_DOUBLE instead.

Heiko Carstens (3):
  mm,slub,x86: decouple size of struct page from CONFIG_CMPXCHG_LOCAL
  mm,x86,um: move CMPXCHG_LOCAL config option
  mm,x86,um: move CMPXCHG_DOUBLE config option

 arch/Kconfig             |   14 ++++++++++++++
 arch/x86/Kconfig         |    3 +++
 arch/x86/Kconfig.cpu     |    6 ------
 arch/x86/um/Kconfig      |    8 --------
 include/linux/mm_types.h |    9 ++++-----
 mm/slub.c                |    9 ++++++---
 mm/vmstat.c              |    2 +-
 7 files changed, 28 insertions(+), 23 deletions(-)

-- 
1.7.7.1

--
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/