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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090428100023.GA18148@uranus.ravnborg.org>
Date:	Tue, 28 Apr 2009 12:00:23 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
	hpa@...icro.com, tglx@...utronix.de, hpa@...ux.intel.com,
	jeremy.fitzhardinge@...rix.com, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86: linker script: avoid ALIGN statements inside output sections

> 
> Below is hpa's fix merged up by me on top of your cleanups. That 
> merge-up is incomplete as we lose these fixlets.
> 
> And in this form it's visible how we lose those cleanups you did - 
> which werent really cleanups ... Please keep such side-effects apart 
> from truly mechanic cleanups, whenever possible - it makes life 
> really simpler.

The cleanup that you applied did NOT move any ALIGN() - or
at least not on purpose.
It was supposed to be a noop from a functionality point of view.

I have started to unify the the two vmlinux.lds files for
32 and 64 bit - and as part of that serie (yet to be published) you will
see individual commits where ALING() is moved and secitons
are reordered etc.
I do this in baby steps so we can track regressions using bisect.

The work is done on top of x86/kbuild and I will rebase as needed when
I have it ready.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ