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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0912211944050.19919@dr-wily.mit.edu>
Date:	Mon, 21 Dec 2009 19:53:50 -0500 (EST)
From:	Tim Abbott <tabbott@...lice.com>
To:	richard -rw- weinberger <richard.weinberger@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION] um: CONFIG_STATIC_LINK=y broken

On Tue, 22 Dec 2009, richard -rw- weinberger wrote:

> This is the bad changeset:

Thanks for tracking that down.  INIT_TEXT_SECTION is:

#define INIT_TEXT_SECTION(inittext_align)                               \
        . = ALIGN(inittext_align);                                      \
        .init.text : AT(ADDR(.init.text) - LOAD_OFFSET) {               \
                VMLINUX_SYMBOL(_sinittext) = .;                         \
                INIT_TEXT                                               \
                VMLINUX_SYMBOL(_einittext) = .;                         \
        }

So there are only 3 code changes here:
(1) wrapping _sinittext and _einittext in VMLINUX_SYMBOL
(2) Adding the AT(ADDR(.init.text) - LOAD_OFFSET)
(3) The added ALIGN(PAGE_SIZE) before the start of .init.text.

I don't yet see why any of these would be problematic; would you be 
willing to try them and figure out the precise cause?

I suspect it'd be easiest for you to try those individual changes 
interactively, but if it's not trivial for you, I'd be happy to generate a 
patch series splitting out this change into pieces for you to bisect.

	-Tim Abbott
--
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