linux-kernel - Re: [REGRESSION] um: CONFIG_STATIC

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.0912211926100.19919@dr-wily.mit.edu>
Date:	Mon, 21 Dec 2009 19:27:57 -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

The individual chunks of that patch are all independent; could you 
determine which one of the changes causes the problem?

	-Tim Abbott

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

> Hi,
> 
> CONFIG_STATIC_LINK=y is broken since 2.6.32.
> The linux binary segfaults immediately.
> 
> This patch introduced the regression (bisected):
> 5d150a97f9391f5bcd7ba0d59d7a11c3de3cea80 is first bad commit
> commit 5d150a97f9391f5bcd7ba0d59d7a11c3de3cea80
> Author: Tim Abbott <tabbott@...lice.com>
> Date:   Thu Sep 24 10:36:20 2009 -0400
> 
>     um: Clean up linker script using standard macros.
> 
>     Signed-off-by: Tim Abbott <tabbott@...lice.com>
>     Cc: Jeff Dike <jdike@...toit.com>
>     Cc: user-mode-linux-devel@...ts.sourceforge.net
>     Acked-by: Sam Ravnborg <sam@...nborg.org>
>     Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
> 
> :040000 040000 43c1b7afe756beb0dc5073195916d54ac41e7546
> fe33dda7c1b15c61a6a65195cc6522beb25e7ba2 M      arch
> 
> Cheers,
> //richard
> 
--
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/