linux-kernel - Issues with "x86, um: switch to generic fork/vfork/clone" commit

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

Message-ID: <CANN689FmsFBjfiD8V-nQyDh+GtTF5B3SDUcuXc=3OeeN6JW0kw@mail.gmail.com>
Date:	Fri, 9 Nov 2012 20:36:53 -0800
From:	Michel Lespinasse <walken@...gle.com>
To:	Al Viro <viro@...iv.linux.org.uk>, linux-next@...r.kernel.org
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Hugh Dickins <hughd@...gle.com>
Subject: Issues with "x86, um: switch to generic fork/vfork/clone" commit

Hi,

I'm having an issue booting current linux-next kernels on my test
machines. Userspace crashes when it's supposed to pivot to the rootfs.
With the loglevel=8 kernel parameter, the last messages I see are:

Checking root filesystem in pivot_root init.
[    6.252717] usb 2-1: link qh256-0001/ffff880853ec9ab8 start 1 [1/0 us]
[    6.259419] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0000
[    6.292302] traps: hotplug[1633] general protection ip:f767c06b
sp:ffbb2d1c error:0 in libc-2.3.6.so[f7652000+126000]

I ran a bisection and it turns out that
e52d03a3775841cc68d0ea9d86f2f09b603c41e6 (x86, um: switch to generic
fork/vfork/clone) is the commit breaking my setup. When reverting
that, I am able to boot linux-next (or mmotm, which is what I was
trying to do in the first place) without issues.

Sorry for not having a more complete root cause at the moment - I'm
lacking some context as to what the change is trying to do.

-- 
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
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/