| 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
| ||
|
Message-ID: <B4E6F7EB08816A4692C7420D7E8F8CBD16EC546E@ORSMSX101.amr.corp.intel.com> Date: Wed, 26 Oct 2011 23:04:04 +0000 From: "Hebenstreit, Michael" <michael.hebenstreit@...el.com> To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: FATAL: kenrel too old - message Can someone explain me why even an ldd on a dynamic executable gives a "kernel too old"? I understand that linking to a gcc that does not support the kernel causes this problem at runtime, but why does ldd fail? Are there other ways to diagnose this? Thanks Michael $ file ./ac_knc ./ac_knc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.34, not stripped $ ./ac_knc FATAL: kernel too old $ ldd ./ac_knc FATAL: kernel too old ------------------------------------------------------------------------ Michael Hebenstreit Senior Cluster Architect Intel Corporation Software and Services Group/HTE 2800 N Center Dr, DP3-307 Tel.: +1 253 371 3144 WA 98327, DuPont UNITED STATES E-mail: michael.hebenstreit@...el.com -- 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