lkml.org 
[lkml]   [2010]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    Subject2.6.33-rc8 breaks UML with Restrict initial stack space expansion to rlimit
    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


    \
     
     \ /
      Last update: 2010-02-14 18:13    [W:0.021 / U:29.368 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site