linux-kernel - Re: [PATCH v1] uml: remove support for 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: <1406826345.111805.1575933346955.JavaMail.zimbra@nod.at>
Date:   Tue, 10 Dec 2019 00:15:46 +0100 (CET)
From:   Richard Weinberger <richard@....at>
To:     Brendan Higgins <brendanhiggins@...gle.com>
Cc:     Jeff Dike <jdike@...toit.com>,
        anton ivanov <anton.ivanov@...bridgegreys.com>,
        Johannes Berg <johannes.berg@...el.com>,
        linux-um <linux-um@...ts.infradead.org>,
        linux-kernel <linux-kernel@...r.kernel.org>, davidgow@...gle.com
Subject: Re: [PATCH v1] uml: remove support for CONFIG_STATIC_LINK

----- Ursprüngliche Mail -----
> Von: "Brendan Higgins" <brendanhiggins@...gle.com>
> An: "Jeff Dike" <jdike@...toit.com>, "richard" <richard@....at>, "anton ivanov" <anton.ivanov@...bridgegreys.com>
> CC: "Johannes Berg" <johannes.berg@...el.com>, "linux-um" <linux-um@...ts.infradead.org>, "linux-kernel"
> <linux-kernel@...r.kernel.org>, davidgow@...gle.com, "Brendan Higgins" <brendanhiggins@...gle.com>
> Gesendet: Dienstag, 10. Dezember 2019 00:02:48
> Betreff: [PATCH v1] uml: remove support for CONFIG_STATIC_LINK

> CONFIG_STATIC_LINK appears to have been broken since before v4.20. It
> doesn't play nice with CONFIG_UML_NET_VECTOR=y:
> 
> /usr/bin/ld: arch/um/drivers/vector_user.o: in function
> `user_init_socket_fds': vector_user.c:(.text+0x430): warning: Using
> 'getaddrinfo' in statically linked applications requires at runtime the
> shared libraries from the glibc version used for linking

This is nothing serious.

> And it seems to break the ptrace check:
> 
> Checking that ptrace can change system call numbers...check_ptrace :
> child exited with exitcode 6, while expecting 0; status 0x67f
> [1]    126822 abort      ./linux mem=256M

Didn't we fix that already?

> (Apparently, a patch was recently discussed that fixes this - around
> v5.5-rc1[1] - but the fact that this was broken for over a year
> remains.)
> 
> According to Anton, PCAP throws even more warnings, and the resulting
> binary isn't really even static anyway, so there is really no point in
> keeping this config around[2].

What?
Anton, please explain. Why is it not static when build with CONFIG_STATIC_LINK?

Thanks,
//richard