linux-kernel - kernel 3.4-rc1 : chroot issues

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>] [day] [month] [year] [list]

Date:	Sun, 1 Apr 2012 18:07:18 +0200
From:	Toralf Förster <toralf.foerster@....de>
To:	linux-kernel@...r.kernel.org
Subject: kernel 3.4-rc1 : chroot issues

When I chroot into a user mode linux image at a stable Gentoo Linux system then either /bin/bash itself crashes immediately or the next command like "emerge --info python" 
within the chrooted environment produces a core dump (of python in this case).

I tried to analyze the core file with gdb (outside of the chroot and yes- it is not very useful b/c python of the UML image was compiled without debug info) but gdb gives :

GNU gdb (Gentoo 7.3.1 p2) 7.3.1
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /mnt/loop/usr/bin/python2.7...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New LWP 28135]

warning: Can't read pathname for load map: Input/output error.

warning: .dynamic section for "/lib/libpthread.so.0" is not at the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/lib/libdl.so.2" is not at the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/lib/ld-linux.so.2" is not at the expected address (wrong library or version mismatch?)
[Thread debugging using libthread_db enabled]
linux-thread-db.c:1062: internal-error: attach_thread: Assertion `ti_p->ti_tid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
linux-thread-db.c:1062: internal-error: attach_thread: Assertion `ti_p->ti_tid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n)  y

I attached both the backtrace of the crash of gdb itself as well as the kernel .config file

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

View attachment "gdb.txt" of type "text/plain" (3718 bytes)

View attachment "config" of type "text/x-mpsub" (73093 bytes)