linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130119063808.GN4939@ZenIV.linux.org.uk>
Date:	Sat, 19 Jan 2013 06:38:08 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Nicolas Dichtel <nicolas.dichtel@...nd.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Issues with "x86, um: switch to generic fork/vfork/clone" commit

On Mon, Jan 14, 2013 at 10:42:10AM +0100, Nicolas Dichtel wrote:
> Hi,
> 
> I'm running a virtual host (kvm/qemu x86 32 bits 16 CPUs, debian
> wheezy) over a x86 64bits target.
> The virtual host has problem during the boot with recent kernels
> (sometimes, daemons crash, but not always, and not always the same
> daemon). Here is an example:
> [    2.150274] input: ImExPS/2 Generic Explorer Mouse as
> /devices/platform/i8042/serio1/input/input3
> udevd[468]: timeout: killing 'firmware.agent' [587]
> 
> udevd[468]: 'firmware.agent' [587] terminated by signal 9 (Killed)
> 
> done.
> 
> [snip]
> 
> [   64.313636] kbd[2563]: segfault at 9fe ip 000009fe sp b758293c
> error 4 in dash[8048000+18000]
> 
> After bisecting, the following commit seems responsible:
> 1d4b4b2994b5fc208963c0b795291f8c1f18becf (x86, um: switch to generic
> fork/vfork/clone)

Er...  Bisect of the guest kernel, I take it?  Could you check if building
the guest !SMP affects anything?
--
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/