linux-kernel - [PATCH v2 0/3] Linker script cleanup patches for alpha

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: <1253119119-18956-1-git-send-email-tabbott@ksplice.com>
Date:	Wed, 16 Sep 2009 12:38:36 -0400
From:	Tim Abbott <tabbott@...lice.com>
To:	linux-kernel@...r.kernel.org
Cc:	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	Richard Henderson <rth@...ddle.net>,
	linux-alpha@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>,
	Tim Abbott <tabbott@...lice.com>
Subject: [PATCH v2 0/3] Linker script cleanup patches for alpha

This is an updated version of the patch series I sent in late July
cleaning up the alpha architecture's linker scripts.  There are some
fixes based on comments from Richard Henderson; it has also been
rebased on top of Linus's current master.

This cross-architecture linker script cleanup project is in
preparation for adding support for building the kernel with
-ffunction-sections -fdata-sections, which is a prerequisite for
Ksplice.

Geoffrey Thomas (1):
  alpha: Clean up linker script using new linker script macros.

Tim Abbott (2):
  alpha: use .data.init_task instead of .data.init_thread.
  Optimize the ordering of sections in RW_DATA_SECTION.

 arch/alpha/kernel/init_task.c     |    5 +-
 arch/alpha/kernel/vmlinux.lds.S   |   95 ++++---------------------------------
 include/asm-generic/vmlinux.lds.h |    4 +-
 3 files changed, 14 insertions(+), 90 deletions(-)

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