lkml.org 
[lkml]   [2008]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.6.24 regression: deadlock on coredump of big process
    KAMEZAWA Hiroyuki wrote:
    > On Mon, 28 Apr 2008 11:11:46 -0400
    > Tony Battersby <tonyb@cybernetics.com> wrote:
    >
    >
    >> Below is the program that triggers the deadlock; compile with
    >> -D_REENTRANT -lpthread.
    >>
    >>
    > What happens if you changes size of stack (of pthreads) smaller ?
    > (maybe ulimit -s will work also for threads.)
    >
    > Thanks,
    > -Kame
    >
    >
    >

    If I leave more memory free by changing the argument to
    malloc_all_but_x_mb(), then I have to increase the number of threads
    required to trigger the deadlock. Changing the thread stack size via
    setrlimit(RLIMIT_STACK) also changes the number of threads that are
    required to trigger the deadlock. For example, with
    malloc_all_but_x_mb(16) and the default stack size of 8 MB, <= 5 threads
    will coredump successfully, and >= 6 threads will deadlock. With
    malloc_all_but_x_mb(16) and a reduced stack size of 4096 bytes, <= 8
    threads will coredump successfully, and >= 9 threads will deadlock.

    Also note that the "free" command reports 10 MB free memory while the
    program is running before the segfault is triggered.

    Tony



    \
     
     \ /
      Last update: 2008-04-29 16:13    [W:4.651 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site