Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752168Ab0BNRLl (ORCPT ); Sun, 14 Feb 2010 12:11:41 -0500 Received: from 128-177-27-249.ip.openhosting.com ([128.177.27.249]:55544 "EHLO jmalinen.user.openhosting.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752090Ab0BNRLj (ORCPT ); Sun, 14 Feb 2010 12:11:39 -0500 X-Greylist: delayed 1865 seconds by postgrey-1.27 at vger.kernel.org; Sun, 14 Feb 2010 12:11:39 EST Date: Sun, 14 Feb 2010 18:40:23 +0200 From: Jouni Malinen To: Michael Neuling , KOSAKI Motohiro Cc: linux-kernel@vger.kernel.org Subject: 2.6.33-rc8 breaks UML with Restrict initial stack space expansion to rlimit Message-ID: <20100214164023.GA2726@jm.kir.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2313 Lines: 50 It looks like the commit 803bf5ec259941936262d10ecc84511b76a20921 (fs/exec.c: restrict initial stack space expansion to rlimit) broke my user mode Linux setup by somehow preventing system setup from running properly (or killing some processes that try to mount things, etc.). This commit turned up as the reason based on git bisect and reverting it fixes my UML test setup (Ubuntu 9.10 on both host and in UML and AMD64 arch for both). I have no idea what exactly would be the main cause for this issue, but this looks like a somewhat unfortunately timed regression in 2.6.33-rc8. The failed run shows like this (with current linux-2.6.git): ... EXT3-fs (ubda): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) readonly on device 98:0. IRQ 3/console-write: IRQF_DISABLED is not guaranteed on shared IRQs IRQ 2/console: IRQF_DISABLED is not guaranteed on shared IRQs IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs mountall: mount /sys/kernel/debug [218] killed by KILL signal mountall: Filesystem could not be mounted: /sys/kernel/debug mountall: mount /dev [219] killed by KILL signal mountall: Filesystem could not be mounted: /dev mountall: mount /tmp [220] killed by KILL signal mountall: Filesystem could not be mounted: /tmp mountall: mount /var/lock [222] killed by KILL signal mountall: Filesystem could not be mounted: /var/lock ... With 803bf5ec reverted, UML comes up and the output looks like this: ... EXT3-fs (ubda): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) readonly on device 98:0. IRQ 3/console-write: IRQF_DISABLED is not guaranteed on shared IRQs IRQ 2/console: IRQF_DISABLED is not guaranteed on shared IRQs IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs init: procps main process (226) terminated with status 255 fsck from util-linux-ng 2.16 ... -- Jouni Malinen PGP id EFC895FA -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/